But field names are also function names, which are values, and live in the same namespace. That's what makes it so confusing (to me). If you fail to see those two little . then you end up reading the code completely wrong. It remains syntactically valid, but fails to type check. But humans are very bad (or perhaps I should say *I* am very bad) at type inference, so it can take a very long time to figure out where the error lies. David On Wed, Sep 9, 2009 at 7:01 PM, John Meacham <john@repetae.net> wrote:
Actually, field names and values are in different namespaces. It just happens that when declaring a field the compiler declares both a field name and a value (a selector) that are textually the same, but otherwise unrelated.
That said, the patch is still a good idea. so applied. thanks!
John