- 17 12月, 2020 3 次提交
-
-
由 Dmitriy Novozhilov 提交于
-
由 Dmitriy Novozhilov 提交于
Also this commit adds AbstractTwoAttributesMetaInfoProcessor which can be used for reporting diagnostics with two attributes (OI/NI, PSI/Light tree)
-
由 Dmitriy Novozhilov 提交于
Update includes: - Changing syntax of `OI/`NI` tags from `<!NI;TAG!>` to `<!TAG{NI}!>` - Fix some incorrect directives - Change order of diagnostics in some places - Remove ignored diagnostics from FIR test data (previously `DIAGNOSTICS` didn't work) - Update FIR dumps in some places and add `FIR_IDENTICAL` if needed - Replace all JAVAC_SKIP with SKIP_JAVAC directive
-
- 15 12月, 2020 1 次提交
-
-
由 Jinseong Jeon 提交于
-
- 11 12月, 2020 2 次提交
-
-
由 Jinseong Jeon 提交于
#KT-43687 Fixed
-
由 pyos 提交于
This is a direct port of JavaAnnotationMapper from the old frontend.
-
- 10 12月, 2020 1 次提交
-
-
由 Mikhail Glukhikh 提交于
-
- 04 12月, 2020 1 次提交
-
-
由 Jinseong Jeon 提交于
-
- 02 12月, 2020 3 次提交
-
-
由 Mikhail Glukhikh 提交于
#KT-43616 Fixed
-
由 Mikhail Glukhikh 提交于
-
由 Ilmir Usmanov 提交于
but not for value classes. Since inline classes and value classes share the same flag, we use presence of the annotation to distinguish them.
-
- 30 11月, 2020 1 次提交
-
-
由 pyos 提交于
Non-const properties may need them too with if the 1.4 feature NoConstantValueAttributeForNonConstVals is disabled.
-
- 26 11月, 2020 4 次提交
-
-
由 Mikhail Glukhikh 提交于
#KT-43332 Fixed
-
由 Mikhail Glukhikh 提交于
-
由 Mikhail Glukhikh 提交于
Before this commit, questionable optimization existed which unwrapped string interpolating call with single argument to this argument. However, this led to source element loss and the necessity of sub-hacks. In this commit we dropped this optimization (anyway user can remove this single-expression string template in code if needed) to keep source elements intact.
-
由 Mikhail Glukhikh 提交于
-
- 18 11月, 2020 2 次提交
-
-
由 Jinseong Jeon 提交于
-
由 Jinseong Jeon 提交于
-
- 16 11月, 2020 6 次提交
-
-
由 Denis Zharkov 提交于
Also that fixes some bugs
-
由 Denis Zharkov 提交于
Use stubReceiver as a receiver for fake calls See issues KT-43358 KT-43359 KT-43378
-
由 Denis Zharkov 提交于
- Put extensionReceiver to candidate even if it's explicit (for sake of clarity) - Split CheckReceiver (dispatch part should only check nullability)
-
由 Denis Zharkov 提交于
Do not try to integrate/postpone receiver expression to the base system Receiver should be resolved independently anyway
-
由 Denis Zharkov 提交于
-
由 Denis Zharkov 提交于
`overriddenMembers` contract requires original (non-enhanced) function See other usages Ignored tests have been working accidentally ^KT-43289 Open
-
- 13 11月, 2020 2 次提交
-
-
由 Dmitriy Novozhilov 提交于
This is needed to avoid clashing name of generated test class (`Nested`) with annotation @Nested from JUnit 5
-
由 Dmitriy Novozhilov 提交于
Previously helpers from checkType.kt was in special package, and if directive was enabled then test runner (`AbstractDiagnosticTest`) injected additional imports to test files and removed them after test was completed. It's very hard to support such behavior in new test infrastructure so there was a decision about changing `CHECK_TYPE`: 1. All helpers from `checkType.kt` now stays in default package 2. `CHECK_TYPE` only adds `checkType.kt` to set of analyzed files and don't modify their content For test which are written in default package (most of tests actually) there are no changes. On the other hand if there is a test where dev want to use checkType functions in testfile with some package then he should explicitly import functions which he needed (`checkSubtype`, `checkType`, `_`)
-
- 12 11月, 2020 2 次提交
-
-
由 Dmitriy Novozhilov 提交于
#KT-39709 Fixed #KT-43156 Fixed
-
由 Jinseong Jeon 提交于
-
- 11 11月, 2020 1 次提交
-
-
由 Mikhail Glukhikh 提交于
This commit includes three changes: 1. 'EnhancedNullability' is no more set for declaration types 2. It is no more used for conversion types in translator 3. Translator inserts implicit not-null cast only when enhanced type is cast to not-null type.
-
- 10 11月, 2020 4 次提交
-
-
由 Denis Zharkov 提交于
-
由 Denis Zharkov 提交于
-
由 Denis Zharkov 提交于
-
由 Denis Zharkov 提交于
Companion as qualifier should be found at static scope not a member one
-
- 06 11月, 2020 3 次提交
-
-
由 Denis Zharkov 提交于
They are not SubstitutionOverrides anymore
-
由 Denis Zharkov 提交于
UPPER_BOUND_VIOLATED for type alias constructors is not supported properly See KT-43142
-
由 Denis Zharkov 提交于
-
- 04 11月, 2020 1 次提交
-
-
由 Jinseong Jeon 提交于
-
- 30 10月, 2020 1 次提交
-
-
由 Mikhail Glukhikh 提交于
In init block or property initializers, for `val x` declared in primary constructor, `x` reference is now resolved to property, not to parameter. So we need two different scopes for primary constructor, one for 'pure' parameters and another one for all parameters, including val/var ones. #KT-42844 Fixed
-
- 27 10月, 2020 1 次提交
-
-
由 Mikhail Glukhikh 提交于
-
- 26 10月, 2020 1 次提交
-
-
由 Mikhail Glukhikh 提交于
-