Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bare sends have to go #121

Open
adrian-thurston opened this issue Jun 18, 2020 · 0 comments
Open

bare sends have to go #121

adrian-thurston opened this issue Jun 18, 2020 · 0 comments

Comments

@adrian-thurston
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant