Ingvar Stepanyan

Sadly, this is the kind of values I do expect in realistic scenarios of systems I'm solving, and they're well off from `f64::EPSILON`, so I expected I'd be fine... >...

FWIW those matrices in my case consist of points on a unit sphere, so yeah, it's very much expected that some coordinates will be close to +-1 while others equal...

(reporter of the referenced issue here) Hm, I actually liked the concise single-line form of Point, while the new form makes it a bit more verbose. I guess it does...

> Ah, have you tried debug printing? It's concise and actually does follow all format specifiers: Huh, I haven't! It's actually a bit surprising that Debug formatting in this case...

> Conversely, fancy many-line 2D layout with unicode block drawing is _worlds_ apart from what you'd expect in `Debug`. Sounds like we're in agreement. For matrix types I'd expect neat...

Looks like PR above addressed dynamic import, but `import.meta` still fails.

> make sure no structs are passed or returned by value across the boundary I think with this restrictions many libraries will sufficiently work on wasm32-unknown-unknown too. WASI target is...

> Could users use WASI for their C/C++ and wasm32-unknown-unknown for their Rust? That's what I've done on few occasions, yeah - but note that they can't use WASI JS...

> Practically speaking wasm-bindgen is incompatible with C/C++. I don't think the original concern is as much about wasm-bindgen itself, as about `wasm32-unknown-unknown` Rust target being incompatible with `wasm32-unknown-unknown` C/C++...

> "wasm-bindgen and C/C+ are fundamentally incompatible", that's just a gotcha to watch out for Yeah it's more like "wasm-bindgen ABI" or whatever we call that compat layer file. >...