#KT-39603 Fixed

 The issue was fixed in df1595e4

 #KT-39630 Fixed

 #KT-39535 Fixed
 #KT-37149 Fixed

Use lexical scope from trace during checking suspend context if the analysis of engaged parent function isn't completed

^KT-39461 Fixed

^KT-39072 Fixed

^KT-39043 Fixed

When there's an explicit one

^KT-39028 Fixed

NB: The test data change at testData/diagnostics/tests/typealias/noApproximationInTypeAliasArgumentSubstitution.fir.kt
is correct: see the relevant non-fir test, the call shouldn't be applicable

^KT-39008 Fixed

^KT-35495 Fixed

 #KT-17341 Obsolete
 #KT-32958 Obsolete

 This issue appeared after recently added new overload for flatMapTo.
 Before that, we picked candidate returning List<T> and completed
 inference, now we also check one more flatMapTo, which is here is
 incorrect and as a result we go into outer scope. Outer scope contains
 one property with deferred type, which introduced error about
 "typechecker has run into recursive problem" even it isn't applicable
 by receiver.

 So, the fix is to check receiver first and only then check return
 type of a candidate.

 #KT-39470 Fixed

 #KT-39033 Fixed

 #KT-38161 Obsolete

 It's important to have ambiguity in these cases to introduce overload
 resolution by suspend-modifier without breaking changes in future

 Relates to #KT-23610

unless the lambda is inline. This way, final field will remain final.

^KT-38444 In Progress

^KT-38444 In Progress

^KT-38444 In Progress

^KT-39050 Fixed

^KT-37321 Fixed