A syntax option (function types versus arrays)

[Neal Gafter]

On Thu, Mar 11, 2010 at 4:24 PM, Jesse Kuhnert <jkuhnert at gmail.com> wrote:
> Now that we've established what 'new' means, any hints from the people
> that know what they're doing where the project is heading?

Alex Buckley was pretty clear that the lambda specification should not
dictate when the allocation occurs.  That is nearly the same thing as
not dictating that each invocation of a lambda expression results in a
distinct value.  In other words, it conflicts with the meaning of
'new'.

This does not work for the conversion to SAM classes, as user code
executes to perform the construction.  That must be visible at compile
time (checked exception checking for exceptions thrown by the
constructor) and runtime (the constructor code executes).  We have yet
to see how project lambda will address that dilemma  So far there is
no proposed syntax for the lambda conversion into which "new" could be
shoehorned.