JetType.isNullable() is not accurate when the type denotes a type parameter: a parameter can be not null (isNullable=false), but its upper bound can be nullable (<T: Any?>), so null may appear in the value of such type. Therefore it's preferred to use a special check (isNullableType()) in codegen from now on Do not generate assertion for parameters of not-null types which have a nullable upper bound + the same with Java method calls Also fix Intrinsics class internal name in tests #KT-3313 Fixed
It renames method parameter to match the name from the overriden method.
That was sometimes resulting with IDE displaying incorrect number of tests in single run.
When compiling from IDE
The condition of a do-while loop can use variables declared in the loop (variables can only be declared inside a block). Previously this behaviour caused crash because after the block was generated, all variables declared inside that block were gone from myFrameMap #KT-3280 Fixed