Jaremy Creechley

This would be great. It's a bit of an oddity this hasn't been in Nimble for a long time.

I started trying to solve this for Atlas, and should be helpful here too: ```nim task buildRelease, "Build release": when defined(macosx): let x86Args = "\"-target x86_64-apple-macos11 -arch x86_64 -DARCH=x86_64\"" exec...

> On my experiments both socketpair and pipe provides same performance and sometimes socketpair is better. The only reason to choose socketpair is that its possible to do read(MSG_PEEK) to...

> the way to do this would be to introduce a pre/post callback which gets enabled by a `config` parameter a bit like future tracking - in that pre/post, you...

> So you got 3 measurement of code between calls to `await`. Is it what you need? I dont see any reasons why `chronos` should have facility to make time...

> I think this is being approached from the wrong end: ie I'd recommend _first_ building a useful end-to-end solution for something concrete - ie something that provides value -...

I took my PR from yesterday and used it to make a more generic solution based on callbacks in `FutureBase`. It's not ready for upstreaming so I left it on...

@matkuki any thoughts on those? Also, have you played with the new "theming" setup?

Great thoughts! You seem to share a fair bit of my own background. I've only done a moderate amount of CSS and Qt as well. - trees won't be too...

Here's how the selectors are currently made: https://github.com/elcritch/fidgetty/blob/2d2a5adf138165c8f5c627afc41ec70cfddb3918/src/fidgetty/themes.nim#L86 Implemented here: https://github.com/elcritch/fidgetty/blob/f021659f18550632ddd678fb4bfaf5142769928e/src/fidgetty/fidget_dev/theming.nim#L96