Loose end: ints(), longs()
spullara at gmail.com
Tue May 28 09:47:15 PDT 2013
I don't care about the new ints() / longs() methods as they seem more for example than actual code. However, I do like the renames.
On May 28, 2013, at 9:41 AM, Joe Bowbeer <joe.bowbeer at gmail.com> wrote:
> I like the renamings you propose.
> I'm not really keen on the ints and longs methods though. I'm already used to intRange, which seems short enough, and is consistent with the other names, none of which are very short.
> On May 28, 2013 9:27 AM, "Brian Goetz" <brian.goetz at oracle.com> wrote:
> Another loose end is a method to generate "all" ints / longs (which are sugar for ranges 0..MAX_VALUE.) These show up in pedagogical examples all the time:
> ints().filter(i -> isPrime(i)).limit(100)
> The logical place for them is:
> but some have raised concern that this might be confusing because we have an instance method on IntStream called "longs()" which widens the elements from int to long. While this isn't fatal, it might be confusing.
> Perhaps it would be better to rename these conversion methods:
> IntStream: longs(), doubles(), boxed()
> LongStream: doubles(), boxed()
> DoubleStream: boxed()
> to asInts(), asLongs(), and asBoxed()?
> In retrospect, these seem better names anyway. And they also eliminate the conflict above.
More information about the lambda-libs-spec-observers