You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
askeksa-google opened this issue
May 2, 2022
· 0 comments
Labels
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
In the VM, this prints false for both runtime type tests, though it should print true for both.
A toString on a runtime type containing a FutureOr of a nullable type seems to never put a ? on the FutureOr type, so it looks like these types are normalized to be declared non-nullable and then erroneously treated as actually non-nullable in the subtype test.
The text was updated successfully, but these errors were encountered:
askeksa-google
added
area-vm
Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
labels
May 2, 2022
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
In the VM, this prints
false
for both runtime type tests, though it should printtrue
for both.A
toString
on a runtime type containing aFutureOr
of a nullable type seems to never put a?
on theFutureOr
type, so it looks like these types are normalized to be declared non-nullable and then erroneously treated as actually non-nullable in the subtype test.The text was updated successfully, but these errors were encountered: