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

Commits on Oct 1, 2024

  1. Make named tuples a standard feature 

     - 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
    odersky committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    87cdbc8 View commit details
    Browse the repository at this point in the history

  2. Update reference docs

    @odersky
    odersky committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    6263944 View commit details
    Browse the repository at this point in the history

  3. Fix ScalaSTM misleading syntax. 

    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 = ...)`.
    @odersky
    odersky committed Oct 1, 2024
    Configuration menu
    Copy the full SHA
    2eb52e4 View commit details
    Browse the repository at this point in the history