Arkadiusz Bulski

What would be the status of UTF16/32? They are still not supported per #187 .

Construct had a substream class that was used by Prefixed field. I am not familiar enough with Kaitai to provide an implementation, just posting it for reference. https://github.com/construct/construct/blob/a06d8dcf7dfe9839d340c1cef723c9b398efb17d/construct/lib/bitstream.py#L139

On some runtimes (those non-statically typed) the **feature might actually be counter productive**. Especially if field inside has only few bytes. Remember that, on Python at least, you are replacing...

Agreed, we need a benchmark.

For C strings, I would recommend that one field would end up adding few fields to resulting struct, with similar names and different types. For example: ```c r->text_array = read_array(io,...

> Another possible way (albeit not way too well-received by many developers) is to roll our own (yet another) implementation of all that stuff, and deal with ks_string*, ks_bytes*, ks_array*,...

@GreyCat I would be willing to start implementing the C runtime. If you would approve, then I would outline the runtime file first (the types and methods for bytearrays etc),...

I have sweat sour feelings about SDS. I really like the idea, I really do, but the implementation is horrible. The repo you linked has bug reports and bugfixes going...

I promised to implement the C runtime, but that was few months ago. Since then I had much work on Construct, and now I am working on few things in...

I agree with Mikhail on this one. Each hint should be discussed as separate feature and I think most of them would be good candidates for AttributeSpec features. And we...