Irfan Baig

Commenting to unstale. This design should be improved, or strongly documented with workarounds/suggestions (and workaround implications).

It should mention in the README what crates and features are necessary to run the examples. Another e.g.: It's not straightforward to people new to the ecosystem that "json" is...

Note, this doesn't prevent me from building my projects or anything -- it's just an error that rust-analyzer spits out while doing its own thing for code analysis.

I just encountered this issue, but was surprised as a slightly older project using Tailwind 4 as a Vite plugin was working fine. First I tried switching to the older...

Hi @Nazariglez, I tested with the draw_bunnymark example built from the develop branch, but it didn't make any difference with the native renderer on my Pixel 8a. It was still...

Tried with the latest notan changes on develop and no change. I tried pixi.js and while their examples don't display very well (in terms of layout) for phones, from what...

Looking into it, I guess I need an https server setup to test wgpu--will look into that later--but let me know if there any other changes I'd have to make...

Yeah, pretty sure, since I was trying to narrow things down. I simply toggle between the below two in Cargo.toml between builds (same machine, same env, etc.), and get the...

> "experimental-threads" Thanks @dajmitonapake ! Adding the "experimental-threads" feature does indeed fix the problem. With the feature enabled, I am able to build with 0.4.3 and not encounter the instantiation...

I use the release profile. Can confirm that "safeguards-release-disengaged", without "experimental-threads", also solves the issue. Is this recommended over "experimental-threads" (until further issue resolution)?