SkytilsMod
SkytilsMod copied to clipboard
Bump jvm from 1.6.21 to 1.7.20
Bumps jvm from 1.6.21 to 1.7.20.
Release notes
Sourced from jvm's releases.
Kotlin 1.7.20
1.7.20
Analysis API
KT-52667
FIR IDE: fun interfaces (SAM interfaces) are not properly resolvedKT-52136
FIR: Implicit type declaration from the other module cannot be used for overloadingAnalysis API. FE1.0
KT-51962
Analysis API: Finish Analysis API for FE1.0Analysis API. FIR
KT-52779
FIR IDE: Import Optimizer cannot handle generic type qualifiersKT-50236
Fix OOB modification trackers for non-Kotlin codeKT-51240
Analysis API: KtAnalysisSession for a specific module cannot create a symbol for PSI that cannot be seen from that module.KT-50868
Analysis API: decompiled type aliases are not resolvedCompiler
KT-53739
Builder inference, extension hides membersKT-53733
Kotlin/Native: update source documentation for the new default memory managerKT-53667
Compiler crashes on attempt to alloc a string on the stack in new MMKT-53480
Internal error in file lowering: java.lang.ClassNotFoundException: com.android.systemui.R$stringKT-52843
Compose: NPE at Parameters.getParameterByDeclarationSlot if inline function with default arguments takes a lambda which captures value class represented by LongKT-51868
JVM / IR: Inconsistent behaviour between lambda expression and SAM interface conversion for the same interfaceKT-53475
Kotlin/Native for iOS: "IllegalArgumentException: Sequence has more than one element"New Features
KT-52495
Support until operator in back-endsKT-52420
Implement resolve of until operatorKT-52419
Implement until operator in the parser
KT-33755
Kotlin/Native: Provide a way to customize a bundle Identifier of a generated frameworkKT-51665
FIR: implement label resolve for "typed this" caseKT-52361
Report warning on potentially empty intersection typesPerformance Improvements
KT-47816
Disable script discovery for non-script environmentsKT-48635
JVM IR: Double/Float values are boxed when comparing for equality in equals method of data/value classesKT-23397
Optimize out field for property delegate when it's safe (JVM)Fixes
KT-53272
Backend Internal error: Exception during IR lowering / No such value argument slot: 2KT-53124
Receiver type mismatch when combining extension properties, type projections, Java sources, and F-bounded type-variablesKT-51868
JVM / IR: Inconsistent behaviour between lambda expression and SAM interface conversion for the same interfaceKT-36770
Prohibit unsafe calls with expected@NotNull
T and given Kotlin generic parameter with nullable boundKT-52974
"IllegalStateException: Symbol with IrSimpleFunctionSymbolImpl is unbound" compiling native targets of MPP project
... (truncated)
Changelog
Sourced from jvm's changelog.
1.7.20
Compiler
New Features
KT-52495
Support until operator in back-endsKT-52420
Implement resolve of until operatorKT-52419
Implement until operator in the parserFixes
KT-53947
IllegalStateException: No mapping for symbol: VALUE_PARAMETER INSTANCE_RECEIVERKT-51234
Context receivers can be duplicated in function declarationKT-51576
Context receivers: "AssertionError: Callers must check that current token is IDENTIFIER followed with '@'" withat
characterKT-49479
JVM / IR: "IllegalStateException: IrErrorType" during IR lowering with non-trivial recursion callsKT-52270
NullPointerException caused by braces on if-else returning a method reference inside lambdaKT-47621
False negative INVISIBLE_MEMBER on call to inaccessible protected synthetic property setterKT-37796
NI: "ISE: Error type encountered" when inferring type of a property that delegates to itselfKT-45430
PSI2IR: "org.jetbrains.kotlin.psi2ir.generators.ErrorExpressionException: null: KtCallExpression: toString()" with recursive function call in "also" block in nontrivial contextKT-52691
K2: Expected FirResolvedTypeRef with ConeKotlinType but was FirImplicitTypeRefImpl with intertwined functional interfacesKT-52822
Fix contract for KtElement.getReference()KT-50223
IndexOutOfBoundsException fromClassicTypeSystemContext$DefaultImpls.getParameter
during call resolutionKT-51963
Change Maven version to 1.7.255KT-47664
Incorrect type checking in the case of generic typesKT-48765
NI: Inferred type does not respect the bound of type variableKT-51243
False positive error "No required context receiver" inside contextual lambdaKT-43541
TYPE_MISMATCH for member function which is not occur for top level function during unsafe castKT-51016
[FIR] False positive OVERLOAD_RESOLUTION_AMBIGUITY between two extensions on different supertypesKT-50155
FIR: support contextual receiversKT-38637
Catch NoSuchFieldException in optimized when expression over enumDocs & Examples
KT-49896
Kotlin/JS: improve-Xir-property-lazy-initialization
description due to making it true by defaultIDE
KTIJ-22286
Kotlin JPS project created via wizard does not contain Kotlin libraries in case of not-released versionKTIJ-22065
IDE notification motivating Kotlin users to use EAPKTIJ-22209
Configure Kotlin on 221 idea adds 1.6.10 Kotlin (despite the fact that IDE plugin is 1.7.10)KTIJ-22171
Fix test BuiltInDecompilerConsistencyTestKTIJ-22016
Empty .kt file and build.gradle.kts can trigger an error while searching for a facade light classIDE. Code Style, Formatting
KTIJ-21346
Incorrect formatting for functions with context receivers and visibility modifiersIDE. Completion
... (truncated)
Commits
7159702
Add changelog for 1.7.209ca25ce
Native: add more tests for Swift Set and Dictionary used in Kotlin1244679
Native: improve thread state switches for NSSet/NSDictionary adapters1abfeb9
[Gradle][MPP] MPP/AGP compatibility: Bump maxSupportedVersion to 7.3b489e93
Fix lowering of receiver access in IR scripting8a8853c
K1. Fix error message for BUILDER_INFERENCE_MULTI_LAMBDA_RESTRICTION608d45c
Add changelog for 1.7.20-RC3a340d2
Fix kind of NoBuilderInferenceWithoutAnnotationRestrictiona17fc51
Fix receiver inconsistency when builder inference restriction disabledf0fd2cf
Put back the line with language feature to 1.7 block- Additional commits viewable 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)
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 detected.
- 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 yourprquantifier.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).
- For PRs that fall outside of the desired spectrum, review the details and check if:
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.