Actually the (x) =&gt; 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.<div>
Having normal functions behave this way doesn&#39;t add anything new. This already exists.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 14, 2012 at 12:30 PM, Rob T <span dir="ltr">&lt;<a href="mailto:rob@ucora.com" target="_blank">rob@ucora.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wednesday, 14 November 2012 at 08:25:30 UTC, Rob T wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Was the single conversion limitation specified by design, or do we have room to expand it to allow for multiple conversions?<br>
<br>
</blockquote>
<br>
</div><a href="http://d.puremagic.com/issues/show_bug.cgi?id=6083" target="_blank">http://d.puremagic.com/issues/<u></u>show_bug.cgi?id=6083</a><br>
<br>
I guess it will be expanded to allow multiple conversions.<span class="HOEnZb"><font color="#888888"><br>
<br>
--rt<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Bye,<br>Gor Gyolchanyan.<br>
</div>