Skip to content
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 121 commits into from
Oct 13, 2020
Merged

Suspend tests #1

merged 121 commits into from
Oct 13, 2020

Conversation

kandersen
Copy link
Owner

No description provided.

4u7 and others added 30 commits October 5, 2020 15:57
Use reference sources of built-in Enum and Comparable instead.

KT-42318
Muted tests failed with `Range must be inside element being annotated` is fixed

Relates to ^KT-38959
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)
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
dzharkov and others added 26 commits October 8, 2020 14:00
- 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 kandersen merged commit 857f107 into kandersen:lvt-tests-update Oct 13, 2020
kandersen pushed a commit that referenced this pull request Jul 18, 2022
kandersen pushed a commit that referenced this pull request Jul 18, 2022
kandersen pushed a commit that referenced this pull request Jul 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.