Dirkjan Ochtman

Results 3119 comments of Dirkjan Ochtman

I think this is less about the precise API and more about which preconditions should be met for the API to still allow access to a functional `Database`.

Another potential direction that mirrors something we have in rustls-native certs: yield both an `Option` and a `Vec` (or similar), and only yield `Some` for the database if the number...

> Overall, I'm mixed on the results and can see this going one in several directions Can you elaborate? What do you like/don't like? What potential directions do you see?

> This seems to be [assert-rs/trycmd#91](https://github.com/assert-rs/trycmd/issues/91) then. @djc Before resolving that issue, maybe we should just accept the hack and use `/` in the snapshots? Seems fine?

Would be nice to split this into smaller commits/PRs so it has less stuff going on all in the same commit.

Just practically, I'm not going to make semver-incompatible changes for this.

@bindiego are you okay with this advisory being published? @lewismosciski the RustSec project by policy typically requires maintainers to consent to advisories. If you're going to file lots of these,...

> One follow-up question: For future reference, what is the policy if a maintainer doesn't respond to a vulnerability report after a reasonable amount of time? Is publishing an advisory...

> I have a strong preference for foo.rs I feel like stating this without any rationale isn't very helpful to the discussion.

> So, I prefer using `foo.rs` just because I adopted the suggestions mentioned by that picture above. It's no matter for me that the `foo.rs` and the `foo/bar.rs` doesn't be...