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

Make named tuples a standard feature #21680

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Make named tuples a standard feature #21680

wants to merge 3 commits into from
+146 −186

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Oct 1, 2024

  • Deprecate experimental language import
  • Make named tuple features conditional on -source >= 3.6 instead
  • Make the NamedTuple object non-experimental.
  • Move NamedTuple it to src-bootstrapped since it relies on clause interleaving which is only standard in 3.6 as well.
  • Drop the experimental.namedTuple import from tests

@odersky
Make named tuples a standard feature
87cdbc8 
 - Deprecate experimental language import
 - Make named tuple features conditional on -source >= 3.6 instead
 - Make the NamedTuple object non-experimental.
 - Move NamedTuple it to src-bootstrapped since it relies on clause interleaving
   which is only standard in 3.6 as well.
 - Drop the experimental.namedTuple import from tests
@odersky
Update reference docs
6263944
@odersky
Fix ScalaSTM misleading syntax.
2eb52e4 
The previous syntax `before copy (name = ...)` is now interpreted as a binary
operation with a named tuple on the RHS. The correct syntax is `before.copy(name = ...)`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@odersky