Alex Andreba

I'll leave here an example i've found if this "feature" causing problems ```rust pub trait Responseable { fn into_stream (self) -> Box; } impl

> ``` > git clone https://github.com/Aandreba/blaze.git > git submodule update --recursive --init > make check > ``` This should probably be added to the README instead of the docs, but...

I just added the [this](https://github.com/Aandreba/blaze/issues/13#issue-1348239505) docs to the main README and to the book

I reckon this may be a problem with Zig assuming it's working on a single-threaded enviroment (which is currently always assumed in Wasm, with no way to opt-out) and doing...

Zig version is listed at the top of the issue (0.11.0-dev.3380+7e0a02ee2), and the code is compiled with this options in the build file ```zig example.shared_memory = true; example.import_memory = true;...

> `make check` worked correctly. `make check` is used to check if the project compiles with all (or at least most) feature combinations. However, `cargo check` (which is what's used...

As for [this](https://github.com/Aandreba/blaze/issues/14#issuecomment-1224611072), the following tests: > ``` > running 6 tests > test boxed ... ok > test col_iter ... ok > test col_major ... ok > test row_iter...

Kind of. If you want to avoid writing C code directly inside a string, you can use the standard library's `include_str!` macro to add the contents of a file directly...

You can write shaders with the **rust-gpu** project and then use [`RawProgram::from_il`](https://docs.rs/blaze-rs/latest/blaze_rs/core/struct.RawProgram.html#method.from_il) to import the generated spv file, but support for importing spv files with the `blaze` macro is still...

I honestly think the default behaviour of checking for posion is a mistake, since it's rarely considered. But it's already consolidated and we are not about to break backwards compatibility...