Static fields in specialized classes

David Chase at
Mon Oct 13 19:16:21 UTC 2014

I think we’ve become accustomed to some of the artifacts that result from erasure-based generics.
That’s not the same as intuitive.


On 2014-10-13, at 3:13 PM, Brian Goetz <brian.goetz at> wrote:

>> As a user, I would *not* expect that there's just one fooCount field for
>> all Foo<T> instances.
> Except that's how generics have worked in Java since 2004.  Do you propose that existing generic code with statics should change how it behaves?  Or are you suggesting that the existing behavior is also counterintuitive?

More information about the valhalla-dev mailing list