Rafael Schouten

But if we have an argument to force looping, in that case we will also need to make a change somewhat as I suggest so that the missing keys in...

That's possible as well, although the problem is table rows usually have all the same properties as the table they come from. So it will break the Tables.jl rows interface.

Where is this at currently? Live streaming midi would be amazing, and I barely even make music anymore. But it would be great for controlling live science visualisations via Reactive.jl...

Sure. I'm guessing a wrapper for [portmidi](http://portmedia.sourceforge.net/portmidi/) would do it, but could be a separate module that depends on MIDI. But who knows if I will ever have time either......

Flatten.jl will handle that (err maybe I misunderstood your use-case). Also have some code here that incorporates lenses and nested tuple flattening into a single process: https://github.com/JuliaObjects/Accessors.jl/issues/9#issuecomment-722130937 I need to...

Yeah, nested `@generated` functions are not easy to reason about. But it usually compiles away completely so it's kind of worth the overhead. Generally do you think something like that...

Requires blocks can invalidate code in other packages, and being at the bottom of a package stack that adds up. Its really which lines, not how many lines, that matters....

My main practical use case now is https://github.com/rafaqz/ModelParameters.jl The main thing missing from Accessors.jl that you can do with Flatten.jl is context about the leaves on the tree that are...

This is most of Flatten.jl I rewrote a while ago for Setfield.jl lenses, with `Query` to get values as a tuple and `Context` to get information about the values (this...

That's cool! I couldn't think of how context would work and still compose with lenses and have the context pass through, or how `set` would work. If I understand this,...