forked from JetBrains/kotlin
-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
Suspend tests #1
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use reference sources of built-in Enum and Comparable instead. KT-42318
This reverts commit 0b822aa
Muted tests failed with `Range must be inside element being annotated` is fixed Relates to ^KT-38959
#KT-42348 fixed
#KT-37987 fixed
Make sure that there is no reference into zombie declarations. - fix KT-40771 - add test
…m several times during code and debug info generation (JetBrains#3792)
…dencies ^KT-42462 fixed
… with it #KT-42457
This allows kotlin-native to generate code in debug mode. LLVM requires debug attributes for this code and SYNTHETIC_OFFSET makes kotlin-native generate dummy debug attributes.
Most of the changes are to the incorrect formatting introduced in d1fd1da.
This is a follow-up to b497f39. It turns out that it didn't help because `IrFunction.returnType` throws exception, and checking for `IrUninitializedType` in `IrType.render` was already too late. Throw and catch specific exception instead. Also add function name into the exception message for better diagnostics elsewhere (can't compute the full FQ name because in cases like KT-42020, the parent is also uninitialized).
Move collectionStubMethodLowering before jvmInlineClassPhase, and make them interact properly. Note that some issues still remain in inline class <-> special bridges interaction. KT-40187 KT-42469
- Rename NullabilityQualifierWithApplicability -> JavaDefaultQualifiers - Use JavaDefaultQualifiers instead of JavaTypeQualifiers for default qualifiers This change is intended to make code more clear and to allow add some additional parameters specific for default qualifiers needed for codeanalysis annotations
Load them as non-flexible when a relevant type parameter has non-flexible upper bound (Currently, it only works for case of codeanalysis annotations)
Currently, only works for codeanalysis annotations because type parameters bounds are enhanced only for them
Also, rename some of the properties It's needed to store status for codeanalysis annotation in that class
Otherwise enhancement algorithm starts forcing lazy mutually recursive computations that leads to RECURSION_IN_SUPERTYPES in complex cases
We have an invariant that their lower bound is always SomeType<Any?> and their upper bound is SomeType<*>. Ehancing the latter to SomeType<out Any> making lower bound not being a subtype of upper bound that breaks contract for flexible types (fails with exception)
Otherwise behavior might change because enhancement may force computation for other type parameters in cases like: class A<X extends Y, Y extends X> {} See the test: org.jetbrains.kotlin.checkers.DiagnosticsTestGenerated.Tests.J_k#testRecursiveRawUpperBound3
The MethodSignatureMapper expected to be able to look at the body of the default argument stub. That is of course not possible when it is from an external dependency. Instead, we go through the attribute owner to get to the method the stub is a default argument adapter for.
kandersen
pushed a commit
that referenced
this pull request
Jul 18, 2022
drop clsDelegate and related ^KT-48773
kandersen
pushed a commit
that referenced
this pull request
Jul 18, 2022
" This reverts commit 3cb2df9.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.