scoping of semantic provider
Currently, our module system uses transitive imports and allows mixing in dynamically scoped extensions.
For editor services, a semantic provider provides the semantic context in which compile-time checking, for instance, is executed. At the moment, we close lexically over editor service definitions, i.e., we store the semantic context that was available at the definition-site of the editor services. Given our current module system, we should use semantic context of the use-site of the editor services instead.Submitted by Sebastian Erdweg on 13 April 2011 at 11:56