News for hackers. Stuff that matters.
Re:How generics were added to .NET by cm2187 on Tuesday March 06, 2018 @04:00AM (#16527733)
But then what is the difference between a a collection of type object and a errasure model generic collection?
Re:How generics were added to .NET by masklinn on Tuesday March 06, 2018 @05:27AM (#16528006)
At runtime? None, it's a static (compile-time) feature, though the compiler does add some type assertions & casts automatically.

Note that this is not necessarily an issue for very statically-typed languages e.g. if I remember correctly GHC uses erased generics (they don't exist at runtime) which works fine because Haskell has neither pervasive RTTI nor specialisation, so the type erasure has ~no runtime visibility or impact.

Re:How generics were added to .NET by kelnos on Tuesday March 06, 2018 @04:13AM (#16527770)
At the VM/bytecode level, not much (if anything?). The benefit comes at compile-time, where the compiler can verify that you're putting the correct types into a collection, and that you're expecting the correct types out.
Re:How generics were added to .NET by SideburnsOfDoom on Tuesday March 06, 2018 @04:29AM (#16527833)
> At the VM/bytecode level, not much (if anything?).

I don't think this is correct. In C# code at runtime, and in the bytecode, you can inspect types for metadata about their generic type params. It is present in the .Net bytecode.

See https://docs.microsoft.com/en-us/dotnet/csharp/programming-g...

> When a generic type or method is compiled into (bytecode), it contains metadata that identifies it as having type parameters.

from https://docs.microsoft.com/en-us/dotnet/csharp/programming-g...

Re:How generics were added to .NET by cm2187 on Tuesday March 06, 2018 @04:57AM (#16527909)
But C# generics aren't erasure model collections are they?
Re:How generics were added to .NET by SideburnsOfDoom on Tuesday March 06, 2018 @07:44AM (#16528442)
No, they are not. The point is, it is different at the bytecode level.
Re:How generics were added to .NET by shellac on Tuesday March 06, 2018 @05:29AM (#16528014)
You've got that completely the wrong way around. An erasing compiler has full access to the type (obviously - it's doing the erasing) and so can verify whether you're putting the correct types in or out of a collection.

Where erasure can cause issues is at runtime. For example:

    X isa List<Int>
Even if X is indeed a list of ints that information isn't held at runtime, so the test can't be supported.

Having said that in some respects this is a C# / Java ecumenical matter. Haskell, for example, doesn't bake types into output code so I suppose it erases even more that java, but it supports very rich polymorphic behaviour.