File tree Expand file tree Collapse file tree 2 files changed +1
-7
lines changed Expand file tree Collapse file tree 2 files changed +1
-7
lines changed Original file line number Diff line number Diff line change 1
1
---
2
- refs/heads/master: 522b6ed8a7112064ca6e15ccb49c76fefae8ff71
2
+ refs/heads/master: ef69ef81e31b248c0eb5ca6b95ab0f302f49e77c
3
3
refs/heads/snap-stage3: 235d77457d80b549dad3ac36d94f235208a1eafb
4
4
refs/heads/try: 49312a405e14a449b98fe0056b12a40ac128be4a
5
5
refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
Original file line number Diff line number Diff line change 29
29
// are unique). Every new node must have a unique id. Avoid cloning HIR nodes.
30
30
// If you do, you must then set the new node's id to a fresh one.
31
31
//
32
- // We must also cache gensym'ed Idents to ensure that we get the same Ident
33
- // every time we lower a node with gensym'ed names. One consequence of this is
34
- // that you can only gensym a name once in a lowering (you don't need to worry
35
- // about nested lowering though). That's because we cache based on the name and
36
- // the currently cached node id, which is unique per lowered node.
37
- //
38
32
// Spans are used for error messages and for tools to map semantics back to
39
33
// source code. It is therefore not as important with spans as ids to be strict
40
34
// about use (you can't break the compiler by screwing up a span). Obviously, a
You can’t perform that action at this time.
0 commit comments