Hannes Greule

I wouldn't expect JSpecify to understand the semantics of the code that is passed as a filter, even e.g. filter(e -> e != null). A fix would be using flatMap or mapMulti where type inference can do a better job. Otherwise you could add a map with requireNonNull after filtering.

It can be used that way (from my basic understanding of lazy val), but it's more powerful semantically and especially performance-wise.

And use the well-known https: label combined with a comment to make sure readers will never look at your code without syntax highlighting again

That sounds interesting and promising. Thanks!

What does "a Java interpreter" mean? Espresso, or something new? Is the plan to make it work transparently (i.e. native code can just load a new class as if it is running in a "normal" JVM) or will it need customization?

As far as I know it's licensing concerns. The first two points at chriswhocodes.com/hsdis/ sound similar to that too.

This seems to be some kind of copy-paste mistake?

"Half the world is telling me to use coroutines because a thread per request is too heavy, the other half a lambda because a computer per request isn't"

— Duncan McGregor

(Source: github.com/jOOQ/jOOQ/is...)

A simple do-while loop in Java, only incrementing an integer 'x', and checking whether x < 10 in the condition. A ' continue' statement after the increment statement confuses IntelliJ.

IntelliJ says the continue is unnecessary, but also says the loop can't complete without throwing an exception. One of those inspections is wrong ;)

To me, the biggest downside is still the fact that it isn't part of the OpenJDK (besides e.g. nixpkgs only providing the community edition).

Which language are you using?

I can't even count how often I *started* workouts unintentionally. I was able to reduce that by rearranging the complications (what a fitting name) on the watch face, so now I only open the compass every now and then.

If you want to collect positions on the edges of an AABB, you DO NOT need to check every position IN the AABB. Directly writing code that only considers the edges is not a premature optimization.

To add insult to injury: the IntelliJ Plugin Verifier mentions usages that do not appear in source code. I guess that's a Kotlin-specific problem.

As I'm releasing from GitHub automatically, that also means that the version is already published there. I'll need to publish a new version that then is released on both GitHub and the marketplace (hopefully), again. I don't think that's in anyone's interest.

The plugin is marked "Compatible" by the IntelliJ Plugin Verifier. However, on the newest IntelliJ release, it is using internal API. For that reason, the plugin was not approved.

The @jetbrains.com Marketplace can be confusing. The IntelliJ Plugin Verifier marks it as Compatible, but as code was marked as internal in the 2024.3, the manual approval didn't go through.

🦋 Hello world 🦋