Quoting myself from the discussion in #4062:

Now the process completes successfully but the resulting document is still buggy.
I'm not referring to small things or missing pieces, but rather that when no section is selected (i.e. no url fragment) I see my declarations, while when root is selected, I only see a bogus main function. Trying to navigate my declarations from the first state doesn

Replace usage of @bitcast with safer alternatives, it needs to work in debug builds

At the moment, zig build only works on a Linux host. Would be nice to include Windows.

Some applets currently have no version number or help message. This probably should be fixed.

// normal comment
fn foo() void {}

/// doc comment
fn foo() void {}

It helps to show that they will be parsed differently.

Needing to load ROMs from the filesystem every time is really annoying. We can easily cache them in localStorage or something.

Also the load cart UI should be rethought to allow for "included ROMs", "saved ROMs", or "load from FOO"

Two approaches:

• rs-gfx portability

Despite the fact it's written in Rust, the produced binary is a standard dynamic library that can be linked to from any program (written in the language of your choice). Typically, you'd need to create a symbolic link with a name that a target application expects, e.g. libvulkan.dylib -> libportability.dylib.

• [

This is to make sure that you can use zigimg to read textures