rfc, associated-type-bounds: resolve question on syntax ambiguity.

Centril · Centril · commit 244d5aac0602 · 2018-01-13T20:41:37.000+01:00
diff --git a/text/0000-associated-type-bounds.md b/text/0000-associated-type-bounds.md
@@ -113,5 +113,4 @@ The introduced form in this RFC is comparatively both shorter and clearer.
 # Unresolved questions
 [unresolved]: #unresolved-questions
 
-- Does this introduce any parsing ambiguities?
 - Does allowing this for `dyn` trait objects introduce any unforseen issues?
