-
I tried searching a bit but could find out which is correct/outdated, some previous comments seem to mention that pointers to storage are illegal however I couldn't find anything about it in the spec …
guusw updated
2 months ago
-
We have made the choice to use existing package managers for distributing WESL code.
One currently unanswered question is how exactly such a WESL project on npm or cargo (or another package manager…
-
Hey there,
this is a quite helpful package. I'm currently looking at primarily your package and the fork wgsl_bindgen.
wgsl_bindgen does a bunch of stuff by default, that I'm not sure I need. Ho…
-
-
imported module is being validated even though it should never be imported
```top.wgsl
fn main() -> u32 {
#ifdef USE_A
return a::func();
#else
return 0u;
#endif
}
```
```mod.wgsl
#d…
-
I think @mehmetoguzderin suggested that the WGSL spec should have a table showing which WGSL builtin function corresponds to which functions or operations in common languages and shader languages, e.g…
-
### System Info
transformers@3.0.0-alpha.6
chrome 127
macos
### Environment/Platform
- [X] Website/web-app
- [ ] Browser extension
- [ ] Server-side (e.g., Node.js, Deno, Bun)
- [ ] Desktop app (…
-
With this wgsl code:
```rust
struct Foo {
xxx: array;
};
fn bar() -> Foo {
return Foo(array(1.0, 2.0, 3.0));
}
```
we get the error:
```
error: expected paren, found `;`
┌─ wgsl:2:17…
-
From WGSL spec: https://gpuweb.github.io/gpuweb/wgsl/#floating-point-types
TODO
- [ ] https://github.com/gfx-rs/wgpu/pull/5476
- [ ] wgsl-in
- [ ] validator
- [ ] msl-out (@FL33TW00D is inter…
-
In https://github.com/gpuweb/gpuweb/pull/1719 we removed the Validation section, and along with it, the concept of standardized error codes.
Us Tint developers are currently trying to decide whethe…