L
Lew
Tom said:Perhaps the confusion here may be due to an ambiguity in the phrase
'generics are erased to ... at runtime'
which I could interpret in two ways. It can mean the something is
actively erasing them at runtime, or it can mean that they have the
static characteristic of having been erased to xxx at runtime. The
first would suggest that type erasure is happening at runtime while
the later implies that erasure has already happened, i.e., at compile
time. While I gather you intended the later, I think someone
inferring the former has a reasonable case too.
I had just finished making essentially the same point moments before I read
your post. Yes, that's the way I mean it - it's not the process of erasure
that interests me, but the static state of having or not having been erased.
Not erased - compile time. Erased - runtime. Therefore erasure (the way I
look at it) is a runtime phenomenon. I don't care if it happened during
compilation or class load.