Primitive collections support breaks existing code

Aleksey Shipilev aleksey.shipilev at oracle.com
Mon Nov 19 07:21:00 PST 2012


Hi there,

I understand primitive streams are still in flux, but those are breaking
the existing test/benchmark code since lambdas are getting inferenced to
primitive interfaces, and implicitly moving to primitive streams (which
is an awesome idea when it is completed :)).

Down to specific questions:

 1. Is there a timeline for skeleton implementations for IntStream? If
that would take longer than, say, a week, I would work that around in
the tests.

 2. Does IntStream.into() omitted for the reason? This does not compile:

    @Test
    public void test3() {
        Assert.assertEquals(
                Arrays.asList(3, 3, 3),
                Arrays.asList("Foo", "Bar", "Baz")
                        .stream()
                        .map((s) -> s.length())
                        .into(new ArrayList<Integer>())
        );
    }

-Aleksey.


More information about the lambda-dev mailing list