The result is something like this (the actual values might vary):
tl.SetT: C3045089 t2.SetT: 51EC8B55 tl.One: 4657F0BA t2.One: 46581CBA
As I anticipated, not only does the SetT method get a different version in memory generated by the compiler for each data type used, but even the One method gets a new version, despite the fact they are all identical.
Moreover, if you redeclare an identical generic type, you'll get a new set of implementation functions. Similarly, the same instance of a generic type used in different units forces the compiler to generate the same code over and over, possibly causing significant code bloat. For this reason if you have a generic class with many methods that don't depend on the generic type, it is recommended to define a base non-generic class with those common methods and an inherited generic class with the generic methods: this way the base class methods are only compiled and included in the executable once.
Was this article helpful?
What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.