Andy Walker

Notes after digging somewhat: the most straightforward implementation would be changing `handleExitCoder` to `handleErrorTypes`, which could use `errors.Is()` and `errors.As()` and either retrofitting `exitError` to implement `Unwrap() error`, or ideally...

Something like this: https://play.golang.org/p/jGF1iYuBl9z

Functional error options are also a possibility: https://play.golang.org/p/HMkLILVU3FP. This has the benefit of only a single type representing all of the things you might want to do specially with user...

Excellent, I see the labels now, but now the outlines are missing! Is there further styling I need to add, or is it just accepted practice to merge the two...

That looks pretty good, I feel like that's more than enough for me to go on. If you feel like this could be actionable in documentation or an examples page...

I may have a couple ides on how to address the issue, but it will take some thinking for how to do it without breaking the API. Will try to...

This is a lot to respond to. I'll test out the new branch, and see if I can get ahold of the activemq.xml, but no, they were not on dead-letter...

A couple months after last working on this issue I actually ended up moving to another company, and most of the work we do here is with Kafka and NSQ,...

I tested walking it through linear rgb and also with integrating the matrices from comments at: https://github.com/LeaVerou/color.js/issues/109#issuecomment-938312745, but the precision failures on oklab->xyz still remain. This isn't my normal area...

If I'm reading this right, another option that occurs is just rebuilding and terminating the daemon if root files are changed. ``` **/*.go !**/*_test.go !cmd/** { prep: //build cmd1 prep:...