[FIR] Add workaround for exception in JavaOverrideChecker.buildErasure
- `useMutableOrEmpty` causes the bounds to be replaced atomically, which avoids the race described in KT-60324. ^KT-60324 fixed ^KT-60445
This commit is contained in:
committed by
Space Team
parent
73032213f0
commit
85c4d6b67b
+2
-1
@@ -345,7 +345,8 @@ object NodeConfigurator : AbstractFieldConfigurator<FirTreeBuilder>(FirTreeBuild
|
||||
}
|
||||
+field(varianceType)
|
||||
+booleanField("isReified")
|
||||
+fieldList("bounds", typeRef, withReplace = true)
|
||||
// TODO: `useMutableOrEmpty = true` is a workaround for KT-60324 until KT-60445 has been fixed.
|
||||
+fieldList("bounds", typeRef, withReplace = true, useMutableOrEmpty = true)
|
||||
+annotations
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user