You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Supporting bare sends is just too risky. Already encountered a case where I did not notice the warning of the ambiguity I had written because there were other warnings present that I was willing to ignore. Also it makes unfair assumptions about whitespace. Perhaps someone wants to write the following, in which case the ambiguity detection cannot work. Finally, an ambiguity in a core area of the language is just not so nice of a design.
send _
"thing to send
One of the main advantages of bare sends is that it reduces program lines when there are many multi-line sends. For example
send _
"line 1
"line 2
It's nice to be able to eliminate the send _ line altogether. If we add a shorthand syntax for send _ we can sneak it in on the first line, assuming all the lines are aligned with one level of indentation.
<< "line 1
"line 2
or
<- "line 1
"line 2
An arrow looks nicer, but << is faster to type.
The text was updated successfully, but these errors were encountered:
Supporting bare sends is just too risky. Already encountered a case where I did not notice the warning of the ambiguity I had written because there were other warnings present that I was willing to ignore. Also it makes unfair assumptions about whitespace. Perhaps someone wants to write the following, in which case the ambiguity detection cannot work. Finally, an ambiguity in a core area of the language is just not so nice of a design.
One of the main advantages of bare sends is that it reduces program lines when there are many multi-line sends. For example
It's nice to be able to eliminate the
send _
line altogether. If we add a shorthand syntax forsend _
we can sneak it in on the first line, assuming all the lines are aligned with one level of indentation.or
An arrow looks nicer, but
<<
is faster to type.The text was updated successfully, but these errors were encountered: