6 Commits

Author	SHA1	Message	Date
Kirill Rakhman	d91000e39c	[FIR] Report INAPPLICABLE_CANDIDATE or more specific diagnostic for callable references ... ... instead of just UNRESOLVED_REFERENCE when something went wrong during resolution. #KT-59401 related	2023-11-08 15:45:48 +00:00
Kirill Rakhman	2f3293f99e	[FIR] Skip redundant INAPPLICABLE_CANDIDATE on call with unresolved callable reference argument ... A new resolution diagnostic UnsuccessfulCallableReferenceAtom is introduced that is used in EagerResolveOfCallableReferences. No diagnostic is reported on unresolved calls with this diagnostic because #KT-59856	2023-07-20 07:29:18 +00:00
Victor Petukhov	42e71f8c53	Remove explicit enabling the new type inference from test data	2022-07-22 16:03:52 +00:00
Jinseong Jeon	bfc7eb7bab	FIR checker: fix REFERENCE_BY_QUALIFIED positioning strategy to consider callable reference	2021-03-26 15:19:10 +03:00
Dmitriy Novozhilov	f283f2db43	[FIR] Improve diagnostic reporting & don't use error symbol for candidate if possible ... Also introduce few new diagnostics: - NONE_APPLICABLE more many inapplicable candidates - HIDDEN for visible candidates	2020-07-28 20:46:56 +03:00
Denis Zharkov	c48539feb3	NI: Fix callable references resolution when LHS is generic nested class ... In case of null qualifier, we should not look into any static scope NB: factory::createCallableProcessor returns NoExplicitReceiver processor in case of null-receiver, that makes resolving the call in the test as `property(::key)` that matches to the property itself, thus leading to overload resolution ambiguity ^KT-35887 Fixed	2020-01-15 16:10:34 +03:00