Juhan Oskar Hennoste

> In jqwik you don't need any dirty tricks since a lifecycle hook can be registered to execute after all jqwik tests have been run. The problematic part when using...

> It's fair to discuss jqwik's programming model. I prefer the current one over the QuickTheories approach because it allows me to leverage the JUnit Platform's way of test discovery,...

Regardless of the specific format chosen, a breaking change I would really like is for the `time` crate to adopt some standard datetime representation as the default or simply get...

I don't really mind the non-human readable variant, since as far as I know there is no widely used binary encoding standard for dates and times. But I think replacing...

> I'm personally not a fan of recent developments in the API of the base64 crate (and I know I'm not the only one), so maybe its mention should be...

> If `encoding_rs` is included, please be sure to mention that its scope is fairly strictly restricted to the [WHATWG Encoding Standard](https://encoding.spec.whatwg.org/), which is focused on the web. (And this...

> I might be missing something but wouldn't the following be just as good? > > ```rust > #[repr(C)] > pub struct Foo { > _marker: core::marker::PhantomData, > } >...

I think out of those two options I would prefer the ability to pass in KSerializer using a new API. I think that as long as that API is cleanly...

> We don't support either... (a quick search suggests it wouldn't even be possible to support WSGI as it's sync only). I might have misunderstood something then. I noticed that...

> It should just automatically do the right thing, i.e. use `Z` when the timezone is UTC. This is what happens in eg. JavaScript. There's no need for a new...