struct

The many faces of struct tags -- Food for thought on how you can better make use of struct tags.

If you're iterating over one or two values in a struct via AoS it's very painful from a memory caching standpoint since you're only getting sizeof(member) / sizeof(struct) efficiency.

Member access syntax can be flattened so that it doesn't matter in the syntax which sub-struct a particular field is in.

At GopherCon, Kyle Erf and Sam Helman gave a great talk about struct tags, how some people are currently using them.

The housekeeping struct has pointers for both the original function and the replaced function.

And at the end of a struct definition, it is a flexible array member.

An old example that comes to mind: I inherited a struct whose memory layout described a wire protocol.

You can effectively define a struct as references to separate sub-structs in separate arrays.

In C99, you could write (struct foo) {a, b, c} without any boilerplate.

Move it's declaration from the hot sub-struct to the cold one and recompile.

What's to stop you passing a struct or object with the two monadic functions attached, or ignore the function requirement (for the case of state) and pass the struct with the state and result in it?

The only real limitation when using cpython was that I could only include a maximum of one other struct in each struct, so sometimes the C header files were a bit strangely written.

This "small introduction" is basically everything there is to know about struct tags.