[Swift-devel] strange behavior evaluating function call as trace arg

Ben Clifford benc at hawaga.org.uk
Sun Feb 8 08:05:33 CST 2009


I'm working in this area, making declarations have both <"mapping 
expressions"> and =assignments. It looks like I'll end up making some 
change like below as part of that.

On Sun, 8 Feb 2009, Ben Clifford wrote:

> 
> On Sat, 7 Feb 2009, Mihael Hategan wrote:
> 
> > In other words, y = f(x) should be:
> > 
> > <assign>
> >   <var>y</var>
> >   <call proc="f">
> >     <var>x</var>
> >   </call>
> > </assign>
> 
> That would fit in with the general trend to not syntactically 
> distinguishing between what used to be datasets and what used to not be 
> datasets.
> 
> Need more markup than the above, though, to accept multiple lvalues in the 
> assignment.
> 
> 



More information about the Swift-devel mailing list