Skip to content

Investigate JEP 395: Records #22297

Open
Open
@tgodzik

Description

@tgodzik
Contributor

JEP 395 introduced record classes which in concept are similar to case classes. Since we are planning to update to a newer JDK at an unspecified future I hope we can figure out if this is in any way useful to use for example for some bytecode optimization similar to #22249

And if we can actually use them or whether it will be impossible for us. This might be binary incompatible, but it would be good to see if maybe we can use this to our advantage in some way without sacrificing binary compatibility

Introduced in JDK 16

Related to #20561

Activity

added
area:jdkIssues tied to artifacts published under a particular jdk
compat:java:jepIssues corresponding to a JEP (JDK Enhancement Proposal)
compat:java:jep:stableIssues corresponding to a JEP which got already delivered as a stable feature in a JDK release
on Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:jdkIssues tied to artifacts published under a particular jdkcompat:java:jepIssues corresponding to a JEP (JDK Enhancement Proposal)compat:java:jep:stableIssues corresponding to a JEP which got already delivered as a stable feature in a JDK releaseitype:enhancement

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @tgodzik@Gedochao

        Issue actions

          Investigate JEP 395: Records · Issue #22297 · scala/scala3