le (and not Collection) stuff can be felt
> so useful and language fundamental, that it should be in the java.lang
> package.
>
> Best regards,
>
> Justin Dekeyser
>
> On Tue, Nov 10, 2020 at 7:02 PM Nir Lisker wrote:
> >
> > Did this discussion get lost?
> &
Did this discussion get lost?
On Sun, Sep 20, 2020 at 1:27 AM Nir Lisker wrote:
> While it might not be difficult to add a find() method to Iterable, why
>> limit it to
>> the find operation, and what about all the other operations available on
>> Stream?
>
>
> Goo
rds for-each loop, or addLast (the latter is
add(list.size()-1, e); ).
- Nir
On Thu, Sep 17, 2020 at 1:32 AM Stuart Marks
wrote:
>
>
> On 9/16/20 1:59 PM, Remi Forax wrote:
> > - Mail original -
> >> De: "Nir Lisker"
> >> À: "core-libs-dev
a Map for every property. So, overall,
I don't think Map is a competitor in this market. It's also possible to
specify that the complexity is linear in an @implNote to avoid surprises.
- Nir
On Wed, Sep 16, 2020 at 11:59 PM Remi Forax wrote:
> - Mail original -
> > De: &q
Hi,
This has probably been brought up at some point. When we need to find an
item in a collection based on its properties, we can either do it in a
loop, testing each item, or in a stream with filter and findFirst/Any.
I would think that a method in Iterable be useful, along the lines of:
public
Hi,
A while back I commented on the suggestion to deal with an annoyance of
casting in a stream [1]. I brought an argument that was used in project
Amber for a similar case.
Like Tagir Valeev, I also see the filter-then-map pattern in various
projects I work on.
I would like to know if this issue
