From a1275c4cb6fbc7483c0064a072f8cb3dbf7193d4 Mon Sep 17 00:00:00 2001
From: Adriaan Moors <adriaan.moors@typesafe.com>
Date: Tue, 25 Mar 2014 16:35:37 -0700
Subject: TODO: binding example

---
 04-identifiers-names-and-scopes.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

(limited to '04-identifiers-names-and-scopes.md')

diff --git a/04-identifiers-names-and-scopes.md b/04-identifiers-names-and-scopes.md
index 57af8afc3e..3086525634 100644
--- a/04-identifiers-names-and-scopes.md
+++ b/04-identifiers-names-and-scopes.md
@@ -34,18 +34,21 @@ in some inner scope _shadows_ bindings of lower precedence in the
 same scope as well as bindings of the same or lower precedence in outer
 scopes. 
 
+<!-- TODO: either the example, the spec, or the compiler is wrong
+
 Note that shadowing is only a partial order. In a situation like
 
 ``` 
-val x = 1;
+val x = 1
 {
-  import p.x;
+  import p.x
   x
 }
 ```
 
 neither binding of `x` shadows the other. Consequently, the
-reference to `x` in the third line above would be ambiguous.
+reference to `x` in the last line of the block above would be ambiguous.
+-->
 
 A reference to an unqualified (type- or term-) identifier $x$ is bound
 by the unique binding, which
-- 
cgit v1.2.3