Mica White
Mica White
From #687 > Furthermore, while the LocalResult is of course correct, I think it would be nice to have some kind of "lossy" output. I would assume that most of...
fixes #5 I'm not confident in the name of this lint. Let me know if you can think of something better changelog: Added the ``[`unnecessary_box_returns`]`` lint to warn when the...
### Summary The lint says that the function below could be made into a `const fn`. Following this suggestion results in a compiler error, which points at x and says,...
The standard library's `Duration` type has two useful methods: - `subsec_micros` - `subsec_millis` This has the benefit of returning a `u32` instead of a `Option`. I suggest the same three...
In the image crate, there's an error type that looks like this: ```rust pub enum ImageError { Decoding(DecodingError), Encoding(EncodingError), Parameter(ParameterError), Limits(LimitError), Unsupported(UnsupportedError), IoError(std::io::Error), } ``` I expect it possible to...
I'd like to see `serde` support in this crate. This would involve creating a new feature, which would be turned off by default. I can only see this being implemented...
According to the documentation of `RwLock` (emphasis mine): > An `RwLock` is poisoned whenever a writer panics while holding an ***exclusive*** lock. This makes sense, since there is no possibility...
Right now, only three iterator types implement `Lockable`: `[T; N]`, `Box`, and `Vec`. It would be nice to have more support for things like `Arc`. I'm not quite sure how...
A previous version of HappyLock supported `ReadLocks` and `WriteLocks` ```rust // when used in a lock collection, it creates a shared lock instead of an exclusive lock pub struct ReadLock