ExpandingMan

In principle yes, but in practice I don't know how many extra steps are required on top of what's already here to implement something like that. In theory I think...

My understanding of how that would work is basically the following: 1. You'd have to use something (perhaps an API call from another package or C++ wrapper?) to give you...

Ok, I did some casual benchmarking. Good news: `List`s don't seem as bad as I was thinking. I was usually seeing in the 40 ns to 60 ns range. Bad...

Have added some fairly extensive unit tests that mostly test whether `getindex` and various `ArrowVector` constructors are working properly. Still need to add more, particularly for writing data.

Yes, I've noticed that. I might actually consider getting rid of some of the constructors, there are probably too many of them, I feel like half of this package is...

Phew... ok I now have in a hell of a lot more unit tests. I haven't seen what the coverage is yet, but now pretty much all of the "important"...

I definitely hope to be able to do things like that. As the design is currently, all you really need is a pointer to a buffer containing binary data in...

Hm, not sure. I tried doing it with `:wm-ignore true` and it does not seem to make a difference. I also tried messing with `:windowtype` but it doesn't seem to...

``` WM_STATE(WM_STATE): window state: Normal icon window: 0x0 I3_FLOATING_WINDOW(CARDINAL) = 1 _NET_WM_DESKTOP(CARDINAL) = 4294967295 _NET_WM_STATE(ATOM) = _NET_WM_STATE_ABOVE, _NET_WM_STATE_STICKY, _NET_WM_STATE_SKIP_TASKBAR, _NET_WM_STATE_SKIP_PAGER WM_HINTS(WM_HINTS): Client accepts input or input focus: True Initial state...

Thought I'd mention, I was messing around in `dunst` today and noticed that they actually have a bunch of different options specifically regarding what to do if something else is...