Renaming to collisions: how Nebula reuses one name across members, and why the CLR tells them apart by signature

Most people picture renaming as a dictionary: every identifier gets its own fresh, meaningless replacement. CalculateTax becomes a, ValidateLicense becomes b, _cachedResult becomes c, and so on down t