azalea/kotlin-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
110,149 Commits 1 Branch 0 Tags
master
Commit Graph

20 Commits

Author SHA1 Message Date
Brian Norman 0881910a1b [FIR] Rewind DFA after call arguments for correct receiver smartcasting 
^KT-63709 Fixed
 2023-12-08 14:32:22 +00:00
Nikolay Lunyak a68a2409d3 [FIR] Remove the applicability filtering when reporting diagnostics 
In case we don't want to introduce any new
abstractions like "user relevance for
applicability", we can just remove the
filtering.

^KT-62541 Fixed
 2023-10-19 09:27:45 +00:00
Kirill Rakhman 640d1e3fc8 [FIR] Fix augmented array set call on smartcasted receiver 
#KT-60917 Fixed
 2023-08-17 15:13:38 +00:00
Nikolay Lunyak 7541732752 [FIR] Fix TEST SPEC tests 
Ensure the test data contents for both the frontends
are identical. This is needed for proper analysis of
K2-differences.
 2023-06-19 07:40:15 +00:00
Kirill Rakhman b2fa104081 [FIR] Keep all failed resolution candidates and fully resolve them 
Previously, when a candidate was found with an applicability that is
better than the current best applicability, all previous candidates were
thrown away. Now we keep them, unless the new applicability is
successful. If no successful candidates are found, we fully resolve all
the unsuccessful ones and select the ones with the least bad
applicability. This improves diagnostics for unresolved calls.

#KT-57844 Fixed
 2023-05-10 11:48:58 +00:00
Kirill Rakhman 5ecf9cce25 [FIR] Don't resolve already resolved qualified access 
^KT-30507 Fixed
 2023-03-02 10:19:53 +00:00
Victor Petukhov 42e71f8c53 Remove explicit enabling the new type inference from test data 2022-07-22 16:03:52 +00:00
Dmitriy Novozhilov ade2307345 [FIR] Fix exponential analysis of augmented array access calls 
^KT-50861 Fixed
 2022-03-11 15:36:05 +03:00
Denis.Zharkov 772579143b FIR: Change semantics for combination of safe calls and operators 
^KT-41034 Fixed
 2022-02-01 13:12:49 +03:00
Jinseong Jeon 03f85bea8f FIR checker: report VAL_REASSIGNMENT on value parameter 2021-06-21 20:58:01 +03:00
Tianyu Geng 6a03f31e50 FIR: add UnsafeCall resolution diagnostics 
Previously unsafe call is reported as part of InapplicableWrongReceiver.
This makes it difficult for the downstream checkers to report different
diagnostics.
 2021-04-19 15:11:13 +03:00
vldf 24f1f1221e Introduce FirInitializerTypeMismatchChecker 2021-04-13 21:36:31 +03:00
Tianyu Geng 761a0a7d0d FIR checkers: report specific errors instead of INAPPLICABLE_CANDIDATE 
Specifically, the report the following 4 errors.

* NON_VARARG_SPREAD
* ARGUMENT_PASSED_TWICE
* TOO_MANY_ARGUMENTS
* NO_VALUE_FOR_PARAMETER

Also added/updated the following position strategies.
* NAME_OF_NAMED_ARGUMENT
* VALUE_ARGUMENTS
 2021-04-02 14:36:14 +03:00
Dmitriy Novozhilov 469252f6b4 [FIR] Don't create smartcast node if smartcasted type is equal to original type 2021-02-20 10:23:33 +03:00
Dmitriy Novozhilov 2b39282682 [FIR] Render original type before smartcasted type in DEBUG_INFO_EXPRESSION_TYPE 
This is made for keep consistency with same renderer in FE 1.0
 2021-02-16 17:51:32 +03:00
Mikhail Glukhikh 7d4eaefd36 FIR: report UNSAFE_CALL on dot when possible 2021-01-29 16:55:26 +03:00
Jinseong Jeon e72ddbcbfe FIR checker: differentiate UNSAFE_CALL from INAPPLICABLE_CANDIDATE 
To do so, inside the root cause of inapplicable candidate errors,
we will record expected/actual type of receiver, if any.
That will help identifying inapplicable calls on nullable receiver.
 2021-01-29 16:54:23 +03:00
Jinseong Jeon b3b09ea9b7 FIR: adjust spec testData after DFA changes: 
* recording type statements for null assignments
* element-wise join by default
 2020-11-04 16:35:42 +03:00
anastasiia.spaseeva 9d862aaa1d [Spec tests] Remove spec info from fir tests 2020-05-26 17:27:06 +03:00
Denis Zharkov 0d34299b7a FIR: Adjust testData for spec tests: dfa 2020-04-21 09:52:52 +03:00