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.

Sign up for GitHub

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

Jump to bottom

Should Send second argument be an identifier instead of an expression? #149

Closed
flbulgarelli opened this issue Jan 22, 2018 · 0 comments
Closed

Should Send second argument be an identifier instead of an expression? #149

flbulgarelli opened this issue Jan 22, 2018 · 0 comments
Labels
question wontfix

Comments

@flbulgarelli
Copy link
Member

flbulgarelli commented Jan 22, 2018 •
edited
Loading

Currently the second argument of a Send constructor - the message - is full-fledged expressions. However, I think that always messages are references and not other kind of expressions.

We could generate the Reference expressions on the fly when traversing the AST.
@flbulgarelli flbulgarelli mentioned this issue Jan 22, 2018
Open
@julian-berbel julian-berbel changed the title Should Send second argument be an identifier instad of an expression? Should Send second argument be an identifier instead of an expression? Jan 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@flbulgarelli