You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/compilers/Design/Bound Node Design.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,8 @@ Generally speaking, that means that there is an isomorphism between the syntax a
9
9
1. Parenthesized expressions do not appear in the bound nodes because they have no semantic meaning.
10
10
2. Query expressions are given a semantic meaning by correspondence to a translated form, so the bound nodes may model the translated form.
11
11
12
+
Default visit order for bound nodes should match order of evaluation, which usually matches lexical order.
13
+
12
14
### Bound nodes should capture all semantic information embedded in the syntax
13
15
14
16
A consumer of the bound nodes should not need to examine the syntax from which they were produced to understand the meaning of the bound nodes. All relevant semantic information that comes from the syntax should be summarized in the fields of the bound node. If a consumer of a bound node needs to refer to the syntax to affect the meaning of the code, that is a design smell.
0 commit comments