Causing a bunch of pain for the user because of a theoretical thing that should be true doesn't help that thing become more true. I feel like we as a people (programmers) fall for this trap too often. Incentives have to be aligned so perfectly for this kind of thing to work.
It's a typing "bug" in code you don't control. In some cases that's enough to not use the library and sometimes it isn't. That's a value judgement based on the developers using the library.
Whatever you do don’t peek at v8, or the c libraries it links, or the operating system underneath it all…
It's a TS "bug", not a Deno "bug" though. TS doesn't have a sound type system. It has type annotations on steroids.
It's neither. It's a bug in the library you're trying to use. The library you're trying to use is broken and you shouldn't use it until the problem is fixed.
It'd be nice if I never had to use software with bugs in it but that's hardly realistic.
“Sorry we can’t use numpy because one of the types in the api is mismatched.”