That is unfortunately more about adding another edge case for the non-reified Java generics system where it has been forced to partially reify, rather than really addressing the larger complaint.
It should address the most common use case for reification. Type erasure has its advantages which we saw in the JVM ecosystem.
I am looking forward to it, and many other things planned for Java!
That's about letting you do Expression<int>, not about removing type erasure or otherwise allowing overloads based on type parameters.
It's one end of the same problem.
int is not an Object, so just erasing is no longer a valid approach, you need to specialize the class/method itself to use int-specific byte code.