Conrad Ludgate

> I thought that temporary scopes are essentially the same between the scrutinee of a `match` and a prefix of a method chain: in either case, temporaries are kept alive...

> But I personally have never run into code using the tap crate in the wild Most people don't want to pull in such a trivial dependency, but also don't...

I would support this, purely because for a while I've wanted some 'string literal macro' system. A way to, in user code, make things like `b"str"`. My main gripe is...

> Moving `"normal"` into a constant without changing `default_animation_wide` to use parentheses (or brackets) would cause an error, which might confuse the programmer. > ```rust > const DEFAULT_ANIMATION: &str =...

> I think I'm amenable to increasing the MSRV for const-generics in a major version bump, but it'd be great if we could identify any other parts of the library...

For now, I'm not in a rush to get this merged in. For my own use cases, noting the performance details above, I ended up making a macro to implement...

I've updated the implementation quite a bit. I've used `array_init` for now to handle the safety of array initialisation. I've also implemented the lazy approach as discussed, I've also changed...

How's this for an implementation? https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=995803e11d0a9af8ba8611832f264ada

The simple solution to that is to just `fuse` the inner iterator before hand. That way it never resumes once `next()` returns `None`

> Said otherwise, it'd be a shame to essentially be duplicating `arrayvec` in here, but it's probably not a good idea to add a dep for it either. I had...