5 ms·
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
by kelnos 9y ago
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.
- SideburnsOfDoom 9y ago> 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-guide/generics/generics-and-reflection 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-guide/generics/generics-in-the-run-time https://docs.microsoft.com/en-us/dotnet/csharp/programming-g...
- cm2187 9y agoBut C# generics aren't erasure model collections are they?
- SideburnsOfDoom 9y agoNo, they are not. The point is, it is different at the bytecode level.
- shellac 9y agoYou'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.