8 Commits

Author	SHA1	Message	Date
Brian Norman	92cb47a8f9	[FIR] Always report when named arguments are not allowed ... #KT-59177 Fixed	2023-06-08 17:25:34 +00:00
Ilya Kirillov	1bbcae5ed2	[FIR] fix resolve contract violation from scopes ... We cannot call lazy resolve to STATUS phase from scopes as scopes may be accessed on a STATUS phase or earlier ^KT-54890 ^KTIJ-23587 fixed	2023-01-13 21:32:51 +00:00
Ilya Kirillov	644d1bf0d0	[FIR] ignore tests which fail because of resolve contracts violation	2022-12-12 16:21:07 +00:00
Nikolay Lunyak	fcd3e4f4c5	[FIR JS] KT-51740: Alter positioning of NO_VALUE_FOR_PARAMETER	2022-09-30 21:39:20 +03:00
Denis.Zharkov	0637748f10	FIR: Introduce NAMED_PARAMETER_NOT_FOUND diagnostic	2021-04-05 12:58:07 +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
Mikhail Glukhikh	de50f8aef3	FIR resolve: add partial support of extension lambda calls ... Here we introduce ONLY_IMPLICIT_RECEIVER tower level to support extension lambda calls on local variables, and soften extension receiver checks to make such extensions visible & applicable. Also here we try to map arguments twice for functional types	2019-12-27 09:57:36 +03:00
Dmitriy Novozhilov	2536fa0cd5	[FIR-TEST] Add new testdata generated after changes in previous commit	2019-12-12 16:11:46 +03:00