- 13 3月, 2021 7 次提交
-
-
由 Ilmir Usmanov 提交于
This reverts commit f4389908.
-
由 Ilmir Usmanov 提交于
This reverts commit bad197e0.
-
由 Roman Artemev 提交于
-
由 Roman Artemev 提交于
Instead of hardcoded `Unit` restore it basing on annotation class and constructor's type arguments
-
由 Roman Artemev 提交于
-
由 Roman Artemev 提交于
-
由 Roman Artemev 提交于
-
- 12 3月, 2021 33 次提交
-
-
由 Roman Artemev 提交于
-
由 Roman Artemev 提交于
Do not ignore compilation errors if they are existed
-
由 Anton Lakotka 提交于
Make native plugin configuration be non-transitive
-
由 Ilya Kirillov 提交于
^KT-45312 fixed
-
由 Ilya Kirillov 提交于
-
由 Alexander Likhachev 提交于
They were broken in 2a8e2613
-
由 Alexander Likhachev 提交于
-
由 Mads Ager 提交于
This breaks from the loop itself which is inconsistent with what happens for breaks in while conditions. Also, the frontend will report that code after the loop is unreachable, which it isn't. :-\ However, those issues are covered in https://youtrack.jetbrains.com/issue/KT-17728, so for now we follow the old backend to not "break" anyone. :) Fixes KT-44412
-
由 Dmitry Petrov 提交于
-
由 Victor Petukhov 提交于
Don't lose upper non-expected type constraints to include them to intersection type during finding the result type of the fixing type variable
-
由 Victor Petukhov 提交于
Those type variable may have other constraints after incorporation into which, the constraint error may appear ^KT-42042 Fixed
-
由 Victor Petukhov 提交于
^KT-43303 Fixed ^KT-42396 Fixed ^KT-42472 Fixed
-
由 pyos 提交于
1. use the correct descriptor in the old backend; 2. clear the temporary variables for arguments in the IR backend. #KT-45292 Fixed
-
由 Ilya Kirillov 提交于
-
由 Ilya Kirillov 提交于
-
由 Ilya Kirillov 提交于
-
由 Ilya Kirillov 提交于
FIR: add tests which checks that every declaration in file has body resolve phase after resolving the fiile
-
由 Ilya Kirillov 提交于
This is not needed as such declarations are now marked with body resolve phase
-
由 Ilya Kirillov 提交于
FIR: mark declarations resolved to BODY_RESOLVE with BODY_RESOLVE phase in implicit body transformer
-
由 Ilya Kirillov 提交于
FIR: render value parameter/lambda/accessor resolve phase if RenderMode.renderDeclarationResolvePhase is enabled
-
由 Alexander Udalov 提交于
-
由 Alexander Udalov 提交于
-
由 Ilya Goncharov 提交于
-
由 Ilya Kirillov 提交于
They will be run only in kotlin-ide plugin
-
由 Igor Yakovlev 提交于
Fixed #KT-45417
-
由 Abduqodiri Qurbonzoda 提交于
-
由 Abduqodiri Qurbonzoda 提交于
-
由 Abduqodiri Qurbonzoda 提交于
-
由 Abduqodiri Qurbonzoda 提交于
-
由 Dmitry Petrov 提交于
KT-42932
-
由 Alexander Likhachev 提交于
-
由 Anton Lakotka 提交于
Make them extend the common CP for sake of backward compatibility ^KT-45020 Fixed
-
由 Tianyu Geng 提交于
Initially I tried adding `mapping` field to `FirArgumentList` but it seems to be very difficult to make it flexible enough to do what I want. So instead, I am creating a `FirPartialResolvedArgumentList`, which seems to be very simple.
-