Changes between Version 10 and Version 11 of TypeDirectedNameResolution


Ignore:
Timestamp:
Nov 19, 2009 8:32:44 AM (6 years ago)
Author:
simonpj@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TypeDirectedNameResolution

    v10 v11  
    299299  f2 r = r.x
    300300}}}
    301 Here the `R.y` in `f1` is an ordinary qualified name.  But what should
    302 `r.x` be allowed?  Remember plain `x` isn't in scope; only `R.x` is.  But
     301Here the `R.y` in `f1` is an ordinary qualified name.  But should
     302`r.x` in `f2` be allowed?  Remember plain `x` isn't in scope; only `R.x` is.  But
    303303we don't want to have to force you to write `r.R.x`, even if we could parse
    304304it!  Maybe TDNR should choose among in-scope x's regardless of whether they are