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
In bytecodealliance/wit-bindgen#406, having imports treated as ES module imports, results in their types no longer being asserted.
The problem is how to assert the imported types, as opposed to the TypeScript compiler checking them against what is being imported.
A type-level assertion type like type AssertType<Expected, Actual extends Expected> = void may be possible if we were outputting a .ts file for the main interface instead of just a declaration, but isn't permitted in the ambient declaration file.
The text was updated successfully, but these errors were encountered:
guybedford
changed the title
gen-host-js: TypeScript type verifications for imports
gen-host-js: TypeScript type verifications for instance imports
Oct 28, 2022
In bytecodealliance/wit-bindgen#406, having imports treated as ES module imports, results in their types no longer being asserted.
The problem is how to assert the imported types, as opposed to the TypeScript compiler checking them against what is being imported.
A type-level assertion type like
type AssertType<Expected, Actual extends Expected> = void
may be possible if we were outputting a.ts
file for the main interface instead of just a declaration, but isn't permitted in the ambient declaration file.The text was updated successfully, but these errors were encountered: