Bump jvm from 1.6.21 to 1.7.10

[dependabot[bot]]

Bumps jvm from 1.6.21 to 1.7.10.

Release notes

Sourced from jvm's releases.

Kotlin 1.7.0

Changelog

Analysis API. FIR

• KT-50864 Analysis API: ISE: "KtCallElement should always resolve to a KtCallInfo" is thrown on call resolution inside plusAssign target
• KT-50252 Analysis API: Implement FirModuleResolveStates for libraries
• KT-50862 Analsysis API: do not create use site subsitution override symbols

Analysis API. FIR Low Level API

• KT-50729 Type bound is not fully resolved
• KT-50728 Lazy resolve of extension function from 'kotlin' package breaks over unresolved type
• KT-50271 Analysis API: get rid of using FirRefWithValidityCheck

Backend. Native. Debug

• KT-50558 K/N Debugger. Error is not displayed in variables view for catch block

Compiler

New Features

• KT-26245 Add ability to specify generic type parameters as not-null
• KT-45165 Remove JVM target version 1.6
• KT-27435 Allow implementation by delegation to inlined value of inline class
• KT-47939 Support method references to functional interface constructors
• KT-50775 Support IR partial linkage in Kotlin/Native (disabled by default)
• KT-51737 Kotlin/Native: Remove unnecessary safepoints on watchosArm32 and iosArm32 targets
• KT-44249 NEW_INFERENCE_NO_INFORMATION_FOR_PARAMETER with type usage in higher order function

Performance Improvements

• KT-48233 Switching to JVM IR backend increases compilation time by more than 15%
• KT-51699 Kotlin/Native: runtime has no LTO in debug binaries
• KT-34466 Use optimized switch over enum only when all entries are constant enum entry expressions
• KT-50861 FIR: Combination of array set convention and plusAssign works exponentially
• KT-47171 For loop doesn't avoid boxing with value class iterators (JVM)
• KT-29199 'next' calls for iterators of merged primitive progressive values are not specialized
• KT-50585 JVM IR: Array constructor loop should use IINC
• KT-22429 Optimize 'for' loop code generation for reversed arrays
• KT-50074 Performance regression in String-based 'when' with single equality clause
• KT-22334 Compiler backend could generate smaller code for loops using range such as integer..array.size -1
• KT-35272 Unnecessary null check on unsafe cast after not-null assertion operator
• KT-27427 Optimize nullable check introduced with 'as' cast

Fixes

• KT-46762 Finalize support for jspecify
• KT-51499 @file:OptIn doesn't cover override methods

... (truncated)

Changelog

Sourced from jvm's changelog.

1.7.0

Analysis API. FIR

• KT-50864 Analysis API: ISE: "KtCallElement should always resolve to a KtCallInfo" is thrown on call resolution inside plusAssign target
• KT-50252 Analysis API: Implement FirModuleResolveStates for libraries
• KT-50862 Analsysis API: do not create use site subsitution override symbols

Analysis API. FIR Low Level API

• KT-50729 Type bound is not fully resolved
• KT-50728 Lazy resolve of extension function from 'kotlin' package breaks over unresolved type
• KT-50271 Analysis API: get rid of using FirRefWithValidityCheck

Backend. Native. Debug

• KT-50558 K/N Debugger. Error is not displayed in variables view for catch block

Compiler

New Features

• KT-26245 Add ability to specify generic type parameters as not-null
• KT-45165 Remove JVM target version 1.6
• KT-27435 Allow implementation by delegation to inlined value of inline class
• KT-47939 Support method references to functional interface constructors
• KT-50775 Support IR partial linkage in Kotlin/Native (disabled by default)
• KT-51737 Kotlin/Native: Remove unnecessary safepoints on watchosArm32 and iosArm32 targets
• KT-44249 NEW_INFERENCE_NO_INFORMATION_FOR_PARAMETER with type usage in higher order function

Performance Improvements

• KT-48233 Switching to JVM IR backend increases compilation time by more than 15%
• KT-51699 Kotlin/Native: runtime has no LTO in debug binaries
• KT-34466 Use optimized switch over enum only when all entries are constant enum entry expressions
• KT-50861 FIR: Combination of array set convention and plusAssign works exponentially
• KT-47171 For loop doesn't avoid boxing with value class iterators (JVM)
• KT-29199 'next' calls for iterators of merged primitive progressive values are not specialized
• KT-50585 JVM IR: Array constructor loop should use IINC
• KT-22429 Optimize 'for' loop code generation for reversed arrays
• KT-50074 Performance regression in String-based 'when' with single equality clause
• KT-22334 Compiler backend could generate smaller code for loops using range such as integer..array.size -1
• KT-35272 Unnecessary null check on unsafe cast after not-null assertion operator
• KT-27427 Optimize nullable check introduced with 'as' cast

Fixes

• KT-46762 Finalize support for jspecify
• KT-51499 @​file:OptIn doesn't cover override methods
• KT-52037 FIR: add error in 1.7.0 branch if run with non-compatible plugins

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pull-request-quantifier-deprecated[bot]]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.kts : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

[dependabot[bot]]

Superseded by #266.