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
TsOptions.eraseTypeAssertions provides JavaScript assertion erasure for consumers that opt in; Calls uses it. The default ETS cast-constraint path remains and still has TODOs for numeric/Boolean and unsupported reference casts.
Remaining acceptance boundary
Complete the remaining default cast semantics or explicitly specify their supported domain. Keep JavaScript assertion erasure distinct from ETS/runtime cast constraints and retain both configuration regressions.
Original report and acceptance context, retained for traceability
We need to add support for cast expression in USVM-TS machine. Seems like the remaining branches should consider only cast from some type to any (creating a fake object) and then cast from this any into a regular type (adding type constraint for the fake object). Otherwise, such situation should be treated as an exception.
Activity
[-]Support cast expression in usvm-ts[/-][+][TS] Support cast expression[/+]