James

Hello, https://jimbxb.github.io/lmhtfy/

This is unfinished. I'd like to make it such that the order of which resources are specified is the order they're passed to the foreign proc. I think I can...

Interleaving can just be done in the verbose way, like: ``` def foreign c interleave(x, y) use foo { foreign c interleave(x, foo, y) } ``` I don't think there's...

Converting to draft while I havent made the relevant changes required.

I can do the doc updates. On coalescing resources, I think this step might not be done yet. It should go into the normalisation phase of resources, which happens just...

An alternative to this could be to support aliases for resources. Something like this: ``` use resource foo.res as foo_res use resource bar.res as bar_res def proc use !foo_res, !bar_res...

I'm thinking also, we could do this at the proc level: ``` def proc use !foo.res as foo_res, !bar.res as foo_res { pass } ``` It has the benefit of...

I like the idea of having aliases for anything that can be exported. Using `from` would introduce a new keyword (which isn't necessarily a bad thing), but I think we...

Yep, I agree. The second would make the construction of a Wybe module from a C module just a little bit easier. And yep, a header file makes more sense....

Well this is annoying. I did mention in #380 about using the LLVM 15 branch. I see that has been committed to in the past 2mos, which is better than...