Actually the (x) => y style delegates compute their return type exactly by looking at the left-hand side. This exact thing is already being done. If the ambiguity cannot be resolved, the return type is explicitly set OR the result is casted to a type. Having normal functions behave this way doesn't add anything new. This already exists.
On Wed, Nov 14, 2012 at 12:30 PM, Rob T <[email protected]> wrote: > On Wednesday, 14 November 2012 at 08:25:30 UTC, Rob T wrote: > >> Was the single conversion limitation specified by design, or do we have >> room to expand it to allow for multiple conversions? >> >> > http://d.puremagic.com/issues/**show_bug.cgi?id=6083<http://d.puremagic.com/issues/show_bug.cgi?id=6083> > > I guess it will be expanded to allow multiple conversions. > > --rt > -- Bye, Gor Gyolchanyan.
