Ingvar Stepanyan

Heh, if it's true, the problem is that it's hard (for now, impossible) to reproduce this bug without LTO, and with LTO it's hard to debug because the code is...

@alexcrichton Hmm I thought I'd check wasm-bindgen's example meanwhile, but that one seems currently broken at the stage of `Scene::new`? Both local build and the [hosted one](https://wasm-bindgen.netlify.app/exbuild/raytrace-parallel/) throw non-descriptive error...

If there would be an update, it would be posted in comments, so no. As I said above, I don't know what's going on here, but you might have more...

See https://github.com/GoogleChromeLabs/wasm-bindgen-rayon/issues/18#issuecomment-960949808 for deeper explanation: > Right, the wording there could certainly be improved. It's hard to convey difference between "main thread" as in "main thread from PoV of Rust...

Did you build with all required flags from README? Most likely, you're missing `+atomics` and company, as that error indicates a non-shared memory.

That is weird. Are you running in a browser that supports Wasm threads? (e.g. if you're on older Safari, it might be not available)

I'm still not sure about this one, because it adds extra string that is only needed for debugging one specific scenario, but will remain in all production builds using bundlers...

Great idea! I suppose one obvious candidate for such metadata is `description` field we already include on posts and could reuse. What else? Should we e.g. include V8 logo as...

Hmm on another hand, the Twitter guideline says: > You should not use a generic image such as your website logo, author photo, or other image that spans multiple pages....

Yeah large image would definitely be messy in this case; it's something that really annoys me about Github when I'm posting issues in chats etc. and everyone sees a huge...