Tomasz Linkowski
Tomasz Linkowski
I've noticed that this issue has not been addressed at all (it's not even labeled) so I hereby make a "ping" :)
> But because Seq now extends Stream and Collectable, I get a conflict because I'm inheriting the same method from two interfaces: > - abstract from Stream > - default...
> Default methods can be a very tricky thing from a backwards-compatibility point of view. It's dangerous to provide default methods, unless there's really no other way... Well, having some...
> I'd agree if there was the possibility to define final methods in interfaces. But without them, I'm not so sure if we can treat default methods just like methods...
> > One caveat: As of Java 8, default methods are not (yet) inlined: http://www.scala-lang.org/blog/2016/07/08/trait-method-performance.html > > I didn't realize that but what I meant is the inlining of static...
OK, as a foreword: I understand that the original proposal consist in moving the implementations from `Seq` **by** making all the (currently `default`) methods in `Seq` `abstract`, and implementing them...
Well, as far as I understand, `SeqUtils.transform` always returns a subset of elements from the source (never adding any elements) so: - it cannot be `SIZED` nor `SUBSIZED` (some element...
Sure, I'll provide a PR. PS. As to response time, I'm absolutely fine with responses in the spirit of "eventual consistency" ;)
Heh, you're right - the analogy is flawed :)
Hm, I took a much closer look and I found the following: - in `Seq.onEmptyGet` we cannot preserve `NONNULL` because the `Supplier` may return `null` - in `Seq.cycle` we cannot...