John McClean
John McClean
When the type changes it breaks left identity ```java Future bindAndUnit = Future.ofResult(10).flatMap(i->Future.ofResult(i+10))); //Future[20] Future applyF = Lambda.λ(i->Future.ofResult(i+10))) .apply(10); //Future[20] ``` But changing the Function to return a Maybe or...
NonEmptyChain will perform better than NonEmptyList. This is a non-backwards compatible change and should be made in Cyclops 11.
Some operations (originally for performance reasons) such as remove / removeAll are always eager. These should respect whatever mode the extended collection is operating in.
**Is your feature request related to a problem? Please describe.** Remove methods deprecated by #1070. A backwards compatibility breaking change. **Describe the solution you'd like** Remove deprecated methods.
Related to #923 flatMap should be type specific. Iterable and Publisher are core types and have flatMap like operators via concatMap and mergeMap Methods (at least of most of them...
It currently accepts an Object based Key. A type parameter should be used.
Related to https://github.com/aol/cyclops/issues/923 Should be the specific type
Years of refactoring (esp. with IntelliJ unconstrained renaming) has resulted in a lot of nonesensical / out of date javadoc. E.g. appendAll for ImmutableQueue states appendAll(T... values)Append values to the...
Native filtering is likely to perform better than filtering via flatMap