diff options
| author | Jeffrey Seyfried <jeffrey.seyfried@gmail.com> | 2016-05-02 00:43:02 +0000 |
|---|---|---|
| committer | Jeffrey Seyfried <jeffrey.seyfried@gmail.com> | 2016-05-02 00:43:02 +0000 |
| commit | ef69ef81e31b248c0eb5ca6b95ab0f302f49e77c (patch) | |
| tree | 078d8373d8f367b06969b23d6f0efd5abe79a934 | |
| parent | 522b6ed8a7112064ca6e15ccb49c76fefae8ff71 (diff) | |
| download | rust-ef69ef81e31b248c0eb5ca6b95ab0f302f49e77c.tar.gz rust-ef69ef81e31b248c0eb5ca6b95ab0f302f49e77c.zip | |
Remove outdated comment
| -rw-r--r-- | src/librustc/hir/lowering.rs | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/src/librustc/hir/lowering.rs b/src/librustc/hir/lowering.rs index 099e13dfa09..0876e609396 100644 --- a/src/librustc/hir/lowering.rs +++ b/src/librustc/hir/lowering.rs @@ -29,12 +29,6 @@ // are unique). Every new node must have a unique id. Avoid cloning HIR nodes. // If you do, you must then set the new node's id to a fresh one. // -// We must also cache gensym'ed Idents to ensure that we get the same Ident -// every time we lower a node with gensym'ed names. One consequence of this is -// that you can only gensym a name once in a lowering (you don't need to worry -// about nested lowering though). That's because we cache based on the name and -// the currently cached node id, which is unique per lowered node. -// // Spans are used for error messages and for tools to map semantics back to // source code. It is therefore not as important with spans as ids to be strict // about use (you can't break the compiler by screwing up a span). Obviously, a |