OvermindDL1

> It's hard to avoid native packages though, and sooner or later you'd face a problem of building one. Unless of course it's a problem specific to erlexec. So maybe...

It just works for me, though I have the full cross-compilation pipeline installed in cygwin (I have to compile ocaml as well).

Hmm I like the explicit constructor, still think a 'when' validation would work well on them to enforce that the right information is stuffed into the type. But I am...

> This mixed validation is where I have mixed feelings (pun intended :wink:). I personally like the mixed validation, as this is a dynamically typed language there is no way...

> Probably won't happen. Better check out j14159/mlfe, but they will have one big problem: static typing on messages from outside. That actually seems like a pretty easy issue to...

Sent too soon, continuing... > Except you wouldn't! Not unless macro constructors are removed, and I actually think they have the biggest value here - more compile time warnings! Look...

Just leaving some notes... So I reduced the mixin to 'just' futzing with the arguments passed to the aabb method and it still causes the stairs issue, which is happening...

Does vanilla MC even have a concept of 'why' a neighbor update happened? Is it remotely possible to get this information in a mod-compatible way? Sure you could mixin to...

For full disclosure, that image only shows creation and iteration and so forth, it does not demonstrate the timings of when components are added and/or removed as is common in...

Awesome @jaynus, looking forward. My minigames tend to do a significant amount of component swapping of a set amount of component types with rare swapping of another set of component...