Patrick Elsen

Results 66 comments of Patrick Elsen

I quite like the idea of using a feature here. Although, some consideration would need to be made, as Cargo performs feature unification. It would be dangerous if there was...

It almost feels like the idea of returning a result gives the most flexibility, because then the caller can decide whether to handle that. Something like: ```rust #[derive(thiserror::Error, Debug)] pub...

Ah, I had not seen that other methods also have assertions. In that case, I don't think returning errors everywhere is a good way to go, because it is too...

Happy to — let's schedule something.

Here's some rules that we have agreed we want. Keep in mind that we don't want to build something that replaces a linter at this point — we only want...

@j-baker, I think I had identified the similar issues as you. Even thought we already do some feature-gating as @mara-schulke suggested, we might have a fundamental issue right now. ##...

I think this is something I am interested in tackling.

Hey @lcmgh! Nice to see you here. What you are describing is definitely something that is on the roadmap. I can summarize our plans to you what I understand from...

I understand, maybe it does not fully make sense for this project. At least I wanted to communicate the idea to you. As someone who maintains a random pattern generator,...

I think the relevant line is [here](https://github.com/danobi/vmtest/blob/7b96f133cb85276292f2c233ab6abcd2e73b109f/src/config.rs#L31). Currently it's defined as a string. I believe you can get this to accept either a string or an array by defining a...