a Platform Group
> Oracle
>
> --
> *From:* core-libs-dev on behalf of Remi
> Forax
> *Sent:* Friday, 19 April 2024 19:47
> *To:* ІП-24 Олександр Ротань
> *Cc:* core-libs-dev
> *Subject:* Re: Addition of Predicate-based findIndex and find
To clear things up, Issues are related to handling using type erasure, not
class generating approach.
вс, 21 апр. 2024 г. в 18:45, ІП-24 Олександр Ротань <
rotan.olexa...@gmail.com>:
> To clear thing up, Issues are related to handling using type erasure, not
> class generating appr
is
some hybrid form of generic handling, where generic maybe be reified on
demand of developer (or implicitly if primitive is used). I am working on
some prototypes at the moment
вс, 21 апр. 2024 г. в 16:31, - :
> On Sun, Apr 21, 2024 at 5:49 AM ІП-24 Олександр Ротань <
> rotan.olexa...@
, - :
> On Sat, Apr 20, 2024 at 8:29 PM ІП-24 Олександр Ротань <
> rotan.olexa...@gmail.com> wrote:
>
>> Gatherers could be effectively terminal, but I don't think Gatherer API
>> designers intended it to be. In related JEP, gatherers are described as a
>> way to decla
But that's topic of another thread
On Sun, Apr 21, 2024, 04:03 - wrote:
> On Sat, Apr 20, 2024 at 7:44 PM ІП-24 Олександр Ротань <
> rotan.olexa...@gmail.com> wrote:
>
>> Also enumerated stream should also support index-aware terminal
>> operations, which getherers are i
developers might just don't be aware of its existence. I think that we as
language devs should think not only about what is possible in language, but
also about is it comfortable and is it obvious for user
On Sun, Apr 21, 2024, 03:36 ІП-24 Олександр Ротань
wrote:
> Yes, I think every possible intermedi
ter, indexed collect, etc. can
> all be done through the indexed gatherer.
>
> On Sat, Apr 20, 2024 at 7:13 PM ІП-24 Олександр Ротань <
> rotan.olexa...@gmail.com> wrote:
>
>> I am sorry, but I feel like I am missing the point of your response and
>> how is it
exed, sink)
> -> return (!filter.test(indexed.index(), indexed.value())) ||
> sink.push(indexed.value()));
> Gatherer wrapped = IndexedGatherer.wrap(filterGatherer); // a
> factory method performing wrapping
> return stream.gather(wrapped) // and more
>
> On Sat, Apr 20, 2024 at
. 2024 г. в 02:33, ІП-24 Олександр Ротань <
rotan.olexa...@gmail.com>:
> Hello again.
>
> I have imagined implementation of enumerated streams in a slightly
> different way. I think enumerated streams should be a separate kind of
> stream like parallel, sequential or some primi
rt
> type-specific operations, partly due to Java's type limits and that Stream
> hierarchy is effectively closed.
>
> Best,
> Chen Liang
>
> On Sat, Apr 20, 2024 at 4:07 PM ІП-24 Олександр Ротань <
> rotan.olexa...@gmail.com> wrote:
>
>> My proposal regarding findIndex bro
re balance
> operations during removal. If we are looking at immutable navigable/sorted
> collections, we can use an array and perform binary search, which works
> just like a tree.
>
> Regards,
> Chen Liang
>
>
> On Sat, Apr 20, 2024 at 3:25 PM ІП-24 Олександр Ротань &
Also, after some research, I found that HashMultisets also have some area
of application in image detection and event simulations
вс, 21 апр. 2024 г. в 01:19, ІП-24 Олександр Ротань <
rotan.olexa...@gmail.com>:
> Sorry for duplicate, I accidentally sent last message only to you
>
og n) to O (log n) could introduce
significant performance improvement, as well as reducing amount of possible
bugs by taking on some of responsibilities related to preserving order of
elements sorted.
вс, 21 апр. 2024 г. в 00:33, Holo The Sage Wolf :
вс, 21 апр. 2024 г. в 01:06, ІП-24 Олекса
; you did with map()), but I don't think either is necessary.
>
> Of course, the big question looming over all of this is -- does this
> feature carry its weight? You and I vote yes, but let's see what the
> community says.
>
> What do you all think? Is this feature worth it
My proposal regarding findIndex brought up a topic that, as I see, has been
brought up here multiple times.
My idea is to extend the existing stream interface in the new
EnumeratedStream interface. Such an approach has a number of advantages.
1. Some methods will be able to explicitly specify
eneral? Of course there
> are use cases, and there are areas in which it is used a lot, but I don't
> believe it is common enough to be part of the std with the one exception of
> concurrent bag.
>
> On Sat, 20 Apr 2024, 23:25 ІП-24 Олександр Ротань, <
> rotan.olexa...@gmail.com>
feel like there could be more to it.
I am not insisting on anything, I just feel that if there is someone (like
me lol) who is willing to take on full development and integration cycle,
there aren't much reason to reject such enhancements.
сб, 20 апр. 2024 г. в 23:43, ІП-24 Олександр Ротань
In this letter I would like to express some of my thoughts regarding the
potential Multiset interface.
I, personally, have encountered a few situations where such an interface
could come in handy, mostly when I needed an ordered collection that
permits duplicates. That time I used guava`s
e reused for
>> findLastIndex)
>>
>> I think if there is no scenario where implementation can do better with
>> findIndex, the findIndex should become a Gatherer, which has better
>> compatibility.
>>
>> Best,
>> Chen Liang
>>
>> On Fri, Apr 1
tempo that
> Java strives for -- compose simple concepts so that you can create what you
> need.
>
> All of that is to say, you have made your point clear. You goal is
> conciseness and ease of access. Understanding that, it's clear that my
> solution is not concise enough to meet th
dex++;
>>> if (predicate.test(element)) {
>>> return downstream.push(index);
>>> }
>>> return true;
>>> }));
>>> }
>>>
>>> and use it like this:
>>> list.stream().gat
Subject
Addition of Predicate-based findIndex and findLastIndex methods to
java.util.List
Motivation
The motivation behind this proposal is to enhance the functionality of the
List interface by providing a more flexible way to find the index of an
element. Currently, the indexOf and lastIndexOf
22 matches
Mail list logo
