---
title: "Discussion on \"Renaming to collisions: how Nebula reuses one name across members, and why the CLR tells them apart by signature\" | Hashnode"
description: "Discussion on \"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"
url: "https://hashnode.com/posts/renaming-to-collisions-how-nebula-reuses-one-name-across-members-and-why-the-clr-tells-them-apart-by/6af328a9ef86d93b24223cd1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Renaming to collisions: how Nebula reuses one name across members, and why the CLR tells them apart by signature](https://delta1labs.hashnode.dev/renaming-to-collisions-how-nebula-reuses-one-name-across-members-and-why-the-clr-tells-them-apart-by?utm_source=hashnode&utm_medium=feed)

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

1d ago · 8 min read · delta1labs.hashnode.dev  
Read the article

-   [#nebulanet](https://hashnode.com/tag/nebulanet)
-   [#obfuscation](https://hashnode.com/tag/obfuscation)
-   [#dotnet](https://hashnode.com/tag/dotnet)
-   [#deepdive](https://hashnode.com/tag/deepdive)

## Written by

[Zero Heartbeat](https://hashnode.com/@clustron)

@clustron

  
[View profile](https://hashnode.com/@clustron)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.