Tyler Bloom
I am still working on docs and tests.
While working on this, it occurred to me that there is nothing specific to Apollo about this. Perhaps this could/should be mirrored and published as a separate crate? I don't...
> Is there a reason you picked fallible_* over try_*? I think a .try_filter() that short-circuits when the predicate returns Err is perfectly We could use `try_*`. That naming definitely...
Perhaps we can do both. Anything that does mapping in a fallible way (i.e. takes `T -> Result`), we call `.fallible_*` and anything that takes a similar closure and we...
Using that, I get a compile-time panic: ``` proc-macro derive panicked message: not yet implemented: https://github.com/JelteF/derive_more/issues/142 ```
Does this not work? Any internal implementation of `min`/`max` would likely work roughly the same. ```rs bag .set_iter() .fold((usize::MAX, usize::MIN), |(min, max), val| (std::cmp::min(min, val), std::cmp::max(max, val))) ```
Sorry, I wrote that example on my phone. The correct example would be this: ```rust bag .set_iter() .fold((usize::MAX, usize::MIN), |(min, max), (_, val)| (std::cmp::min(min, val), std::cmp::max(max, val))) ``` That said,...
I really, really like the listing of invariants and checking them. We should start a doc that lists these things out.
Won't fix
> So, just to be clear, you want an iterator that yields OccupiedEntry for occupied entries and… something else, for vacant entries? Sorry, I should have been more clear. I...