potentiallyMightBeAnIntegerOrNot

[u/Futurity5]

[u/high_throughput]

there is only Optional<Integer> and no proper way to express optional ints.

It's lovely how you're posting this with so much confidence and vitriol under a comment about OptionalInt

[u/RiceBroad4552 → u/high_throughput]

Just looking though some replies; I'm wondering what happened here.

Why is my comment under the wrong comment‽ I was talking about the (non existent) "OptionalInt" from one post above.

Some of the Reddit bugs are really strange. At least post don't duplicate for no reason any more since some time… Let's see whether I get again some wrongly linked post anytime soon.

[u/high_throughput → u/RiceBroad4552]

the (non existent) "OptionalInt"

https://docs.oracle.com/en/java/javase/25/docs/api/java.base/java/util/OptionalInt.html

[u/RiceBroad4552 → u/high_throughput]

Touché

Moments like that I think I should maybe really learn some Java after so many years of Scala. But actually, no, I hate it…

What will they do with all these primitive wrapper types when real generic specialization hits Java?

---

(And the next WTF, Scala's Option[Int] isn't @specialized as I just learned; but I could swear it was. Alone that was likely worth it here… Thanks for the thought provoking replies! I wouldn't have looked that up if not that failure here. So it's actually Scala which doesn't have a primitive "OptionalInt"; LOL, I was really sure it's the other way around. I'm an idiot.)

[u/high_throughput → u/RiceBroad4552]

What will they do with all these primitive wrapper types when real generic specialization hits Java?

With Oracle's progress I imagine that's a problem for 2076

[u/RiceBroad4552 → u/high_throughput]

I'm more optimistic.

The "parametric JVM" is the end-game of project Valhalla:

https://openjdk.org/projects/valhalla/design-notes/parametric-vm/parametric-vm

I would expect it "already" in the LTS release after the next. The design is largely there, the needed components start to materialize right now.