Skip to content

SIP minutes: tweak wording about infix #1659

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

Merged
merged 1 commit into from
Mar 13, 2020
Merged

SIP minutes: tweak wording about infix #1659

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _sips/minutes/2020-03-11-minutes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -218,7 +218,7 @@ Most believe it to be useful, but multiple committee members vocally opposed mak

Also can it be merged with `@jsName`? Seb: Yes, but Scala.js's symbol variant of that would have to remain separate. Seth et al considered that sufficient unification.

`@infix` is uncontroversial, but there is a question of whether to allow non-`@infix`-annotated methods to still be used infix before a curly brace, e.g. `xs map { ....`.
No one in the committee who has registered an opinion is against `@infix`, but there is a question of whether to allow non-`@infix`-annotated methods to still be used infix before a curly brace, e.g. `xs map { ....`.

Conclusion: allow that in 3.0, maybe crack down harder later.

Expand Down