Jake Wharton

> Don't propose updating Java to "unstable" releases, e.g. from v11 to v15 Java 15 was stable when it was released, and it remains stable to this day. It was...

> Doing so should never be the default behavior for Renovate This seems very weird. The version which is supported even longer than the LTS versions is the latest version....

Protesting? I'm trying to have a discussion about it, but it seems like you're not open to engaging with push back. Have a good rest of your 2024.

Thanks for such a detailed issue description. I'll follow along at the coroutines issue for now, as I suspect this behavior is entirely out of our control at this layer.

I would prefer this to be named based on how it behaves, not a relationship to the "normal" `forEach`. If you run this new function on non-random access-based list, you...

I would also recommend try/catching the raw parser, creating a new exception with surrounding context (such as the originating file name), and adding the parser exception as the cause. I...

Yep! Didn't know that existed, but that's the concept for sure.

Hard to know if this is a real issue drowned in AI slop, or just a normal exception that some AI hallucinated as an issue and then drowned in slop.

The proposal makes no mention of `object` and `companion object`. Are there technical limitations to expressing those? Would mirroring the same class and static instance holder structure with the annotation...

Sounds a bit like RxJava's `throttleLatest`. Does that look like what you're asking for? http://reactivex.io/RxJava/3.x/javadoc/io/reactivex/rxjava3/core/Observable.html#throttleLatest-long-java.util.concurrent.TimeUnit-