Philippe Cholet
Philippe Cholet
I tried `ia = IMDb(loggingLevel='NOTSET')` but it lead to an error [here](https://github.com/alberanid/imdbpy/blob/master/imdb/__init__.py#L182) (where imdb name is not defined). I suppose this would be the way to cancel logger prints. But...
There is quite some changes to be released since "0.10.5" right? I think all that should be released, then only then make a release with `it_` prefixes and MSRV bump...
I guess the major con would be the "copy/paste" work on our end (and delete later), and the major pro would be for users to have time to adapt especially...
I was more thinking of mod itertools { pub trait Itertools : Iterator { #[deprecated(note = "Use it_doit version instead, since = "0.12.0")] fn doit(self) where Self: Sized {} fn...
`IntoIterator` is implemented for `&'a GroupBy` (not for `GroupBy`) so `.into_iter()` does not take ownership of `GroupBy` so the `iter.group_by` is dropped at the end of the function while `.into_iter().flat_map()`...
The `Try` trait behind `try_fold` is unstable so we can't specialize them. And I think `try_` methods should use `Try`. We only have one `try_` method: `try_collect` which is in...
Wow... that's bold, intriguing and definitely interesting. I'm curious how it would impact benchmarks (for `Positions` mainly, since `FilterMapOk` might end up deprecated with #844).
@jswrenn I fully read [RFC 2845](https://github.com/rust-lang/rfcs/blob/master/text/2845-supertrait-item-shadowing.md) and saw the associated rust issue where there is a concern about the prelude. The trait `Iterator` is always in scope (because in the...
@Ten0 I only skimmed the changes but I like the idea of this PR (implement `IntoIterator` for both `X` and `&X`), I think it would help solve #665 too. It...
You certainly have a valid argument. However, I don't see how we could avoid that. We don't assume that the type of the initial value is clonable (and doing so...