Skip to content

Fix #8015: update docs #8039

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
Merged
merged 2 commits into from
Jan 20, 2020
Merged

Fix #8015: update docs #8039

merged 2 commits into from
Jan 20, 2020

Conversation

liufengyun
Copy link
Contributor

Fix #8015: update docs

@nicolasstucki nicolasstucki merged commit 619f951 into scala:master Jan 20, 2020
@nicolasstucki nicolasstucki deleted the fix-8015 branch January 20, 2020 09:50
@unkarjedy
Copy link
Contributor

@liufengyun
from docs

In Scala 3.0, both _ and ? are legal names for wildcards.
In Scala 3.1, _ is deprecated in favor of ? as a name for a wildcard. A -rewrite option is available to rewrite one to the other.
In Scala 3.2, the meaning of _ changes from wildcard to placeholder for type parameter.

Scala 3.1 and 3.2 will come not very soon, to put it mildly.
Maybe _ should be left in the grammar until then?

@liufengyun
Copy link
Contributor Author

@unkarjedy there are other deprecated but supported syntaxes that are not reflected in the doc. Adding them to the doc will be confusing.

@nicolasstucki
Copy link
Contributor

Though we should be clear on what syntax we support for migration modes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@nicolasstucki nicolasstucki nicolasstucki approved these changes

Assignees

@nicolasstucki nicolasstucki

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

review and update vararg-patterns Compatibility / Migration docs section
3 participants
@liufengyun @unkarjedy @nicolasstucki