Kirill Zaborsky

@matth- have you seen my last 2 comments in Reviewable? Also recent merges brought some conflicts. Will you have tome to resolve this or maybe you need my help finishing...

Thanks @matth- There is no rush for sure so take your time if you need to. Just let me know if you need some help.

Very basic demo of speed improvements in `strace`: ``` qrilka@qdesktop ~ $ time strace -c -e openat head -1000000 /dev/urandom > /dev/null % time seconds usecs/call calls errors syscall ------...

What about splitting those somehow? E.g. use some categories maybe? Or even alphabetically?

I'm not sure why but switching to GCC 7 on Gentoo resolved this issue for me, like it's described in https://bugs.gentoo.org/644200

@v0d1ch I've tried out a90b6716072c9b2b1cdc87f1c8c2022cd8267711 and it doesn't seem to work properly, See https://gist.github.com/qrilka/49b0634fce17bcbd2cd4abea503a0f8c

Update doesn't seem to change the result. BTW maybe it's worth to fix issue with boolean blindness here? Using `serveWithContext` and opaque `(True :. EmptyContext)` doesn't look quite user-friendly API

It looks like some problem in old Stack adding libiserv into build plan, I couldn't find why that happens yet :-\

@nh2 I have found the reason this happens. It's another occurrence of the same problem Michael wrote about in https://www.snoyman.com/blog/2019/01/mismatched-global-packages . Overriding `time` triggers rebuild for any dependent packages and...

Tried to use 1.1.6 with nested records but failed with value type error ("1" was in a string field), will try to check HEAD and get a test case later