Alignment? Stack strings? Allocator control?

[rygo6]

First, I have to say his project is incredibly impressive. Most of it is exactly how I'd do it myself if I made this, or even better than what I would come up with.

There are a few things though which I see missing. Or I wish could change.

1. There needs to be some way to control struct alignment. Such as the GCC align attribute. But I'd also like to be able to use the C Bitfield syntax in struct declaration.

2. I would like to be able to optionally deal with strings entirely on the stack. Allocate and manipulate strings entirely in stack buffers. Have methods like tostring be able to write them out to stack buffer. Forcing strings to be dealt with on the heap is disruptive to some of the C style of programming.

3. More control of allocators in general would be good. I think maybe taking a few notes from odin or zig might be good here. Where anything that creates an allocation has to have an allocator explicitly passed to it. Or that you could switch the default allocator for an entire scope and have everything in that scope automatically use that. Nothing should be using the heap by default and not be controllable.

4. Someway to make use of data stored in macros in C headers. A lot of Khronos libraries encode a bunch of useful data as C macros. Can see an example here: https://github.com/KhronosGroup/OpenXR-SDK/blob/main/include/openxr/openxr_reflection.h Someway to be able to access that and use it in the nelua preprocessing would be useful.

[IcedQuinn]

Are static strings allocated on the heap? I was of the understanding that C-likes made those pointers to ROM. But I have not checked the Nelua internals here.