How, when and where are generic methods made concrete?

Solution 1:

In C#, the concepts of generic types and methods is supported by the runtime itself. The C# compiler does not need to actually create a concrete version of a generic method.

The actual "concrete" generic method is created at runtime by the JIT, and does not exist in the IL. The first time a generic method is used with a type, the JIT will see if it's been created, and if not, construct the appropriate method for that generic type.

This is one of the fundamental differences between generics and things like templates in C++. It's also the main reason for many of the limitations with generics - since the compiler isn't actually creating the runtime implementation for types, the interface restrictions are handled by compile time constraints, which make generics a bit more limiting than templates in C++ in terms of potential use cases. However, the fact that they are supported in the runtime itself allows creation of generic types and usage from libraries possible in ways that aren't supported in C++ and other compile-time created template implementations.

Solution 2:

The actual machine code for a generic method is created, as always, when the method is jitted. At that point, the jitter first checks if a suitable candidate was jitted before. Which is very commonly the case, the code for a method whose concrete runtime type T is a reference type needs to be generated only once and is suitable for every possible reference type T. The constraints on T ensure that this machine code is always valid, previously checked by the C# compiler.

Additional copies may be generated for T's that are value types, their machine code is different because T values are not simple pointers anymore.

So yes, in your case you'll end up with three distinct methods. The <string> version would be useable for any reference type but you don't have others. And the <int> and <double> versions fit the "T's that are value types" category.

Otherwise an excellent example, the return values of these methods are passed back to the caller differently. On the x64 jitter, the string version returns the value with the RAX register, like any returned pointer value, the int version returns with the EAX register, the double version returns with the XMM0 register.