Ayush

Sounds great but is the goal of this change to make struct-based API more familiar-able(?)? Is it complete omitting of old functions or just a layer/macro on top of existing?

> surround functions by a macro Okay, got it. I use the struct based API throughout all my projects. I do not really mind the presence of glms_ prefix. So...

I think all changes have been resolved.

I generally like this idea but don't like the suggested syntax. Under the current syntax, you just do ``_ = foo`` and ``_ = bar()``. It just simply means that...

After thinking about this a bit, I think there is no simple, practical way to solve this problem. Afterall dependency management is a complicated issue and its not feasible to...

Thanks for the explanation, it makes a lot of sense now. Again sorry for taking it off-topic.

Mach provides a log for wasm. But it cannot be that easily replaced. Providing an alternative reimplementation for the user would be complicated. Same goes for panic for wasm. I...

One more issue with compiling to stage2 is that mach-gpu uses a lot of function pointers, but the semantics of fp are changed in stage2. `fn (args) ret` -> `*const...

For the sake of explaining, lets just assume that Collection is a single archive. Actually having multiple collections only makes sense in case of archives and thats why its there....

The json collection example I initially created didn't take into consideration having multiple collections (in fact it used the word collection for just any folder). So here's an updated one:...