MiniaczQ

AWS's S3 lib is about to be production ready, but I've yet to check if it suffers from the same problems

I've read through the rust article about coverage and some of the source code. Would it be unreasonable to separate `tarpaulin` into lesser CLI apps under the cover? A logical...

If profraw parsing is integrated then yeah, step 2 could be inside step 3 and step 2 would run tests. Later today I'll try to follow the logic through source...

Is there any particular reason why the args use a builder pattern instead of derives? I can see that this 70-line monster was built over 6 years, so maybe it's...

I think an example problem case would be: ```sh cargo tarpaulin --no-run --bin project1 # [...] cargo tarpaulin --skip-clean --bin project2 ``` You can mismatch many more options but simply...

Not right now at least, this issue is about allowing that

Overall I like this solution, it's very flexible when it comes to reading states. I originally thought the computed state is not stored in the world, and instead computed directly...

What would happen if you had 3 states: `Foo` `Bar` and `FooBar` (computed from previous two) and both `Foo` and `Bar` changed in the same tick? Would it trigger one...

Note from me, because it seems like 2 topics are being confused here. Marker states and none-able computed states are __separate__. I too don't see myself using ZSTs for computed...

It's unreasonable to scale that up, it looks fine with one enum, but you will have to do that to every enum. The same 'none' variant to every state. On...