Thanks for the data - I guess the takeaway is that, as expected, making
type-checking of raw typing sharper will help migration (e.g. add type
parameters to existing code that might use some generic signatures
already), but it comes at the cost of some source incompatibility.
If we restrict this only to enums, of course this would be a non-issue;
as you say, enums are non-generic right now, so we have a clean slate
(assuming we're ok with the asymmetry).
Thanks again.
Maurizio
On 10/12/2018 21:35, Liam Miller-Cushon wrote:
On Mon, Dec 10, 2018 at 1:33 PM Brian Goetz <brian.go...@oracle.com
<mailto:brian.go...@oracle.com>> wrote:
Can you clarify: is 1 out of 55Kfiles for the "all raw type refs"
option, or the "only for raw enum refs"? It looks like you are
saying the former?
Yes: 1:55000 was for all raw type refs, with no special-casing of enums.
(The other variation should be fully source compatible for corpuses
that don't contain any generic enums, right?)
