48d5fe9ec5
Currently these have non-traditional APIs which take a buffer and report how much was filled in, but they're not necessarily ergonomic to use. Returning an iterator which *also* exposes an underlying slice shouldn't result in any performance loss as it's just a lazy version of the same implementation, and it's also much more ergonomic! cc #27784 |
||
|---|---|---|
| .. | ||
| Cargo.toml | ||
| collection_impls.rs | ||
| hex.rs | ||
| json.rs | ||
| lib.rs | ||
| serialize.rs | ||