Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8067422

Lambda method names are unnecessarily unstable

    XMLWordPrintable

Details

    • b44
    • Verified

    Backports

      Description

        Currently, when lambda names (for non-serializable lambdas) are generated, the exact name depends on the number of (non-serializable) lamdbas generated so far by the current javac instance. The reason is that the counter for lambda names is not per-file, but per-javac instance. For example, consider:
        public class L1 {
            private Runnable r = () -> { };
        }
        public class L2 {
            private Runnable r = () -> { };
        }
        doing:
        javac L1.java L2.java
        will make L1's lambda use lambda$new$0 and L2's lambda$new$1, while:
        javac L2.java L1.java
        will lead to the opposite name assignment.

        The problem seems to be simple: LambdaToMethod.LambdaAnalyzerPreprocessor.lambdaCount is not reset before starting with a new top-level.

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8085299 Lambda method names are unnecessarily unstable

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8136598 Lambda method names are unnecessarily unstable

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8140949 Lambda method names are unnecessarily unstable

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8142512 Lambda method names are unnecessarily unstable

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8143973 Lambda method names are unnecessarily unstable

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8147318 Lambda method names are unnecessarily unstable

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8148189 Lambda method names are unnecessarily unstable

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8148297 Lambda method names are unnecessarily unstable

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8148312 Lambda method names are unnecessarily unstable

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8148689 Lambda method names are unnecessarily unstable

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8154643 Lambda method names are unnecessarily unstable

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8155494 Lambda method names are unnecessarily unstable

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8161808 Lambda method names are unnecessarily unstable

            • P5 - Cosmetic problem like misspelt words or misaligned text.
            • Resolved

            Activity

              People

                jlahoda Jan Lahoda
                jlahoda Jan Lahoda
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: