We added a new task ResolveAllDefs which resolves a name to all its definitions. The new implementation filters definitions on the fly w.r.t. some properties. There is another ResolveAllDefs task, which resolves all names in a given scope. It’s implementation first resolves the names and filters them in a subsequent task.

Both tasks might be implemented in a similar way. For example, the on-the-fly filtering of the first task might not be needed but can be done in a subsequent task, similar to the second task implementation

Submitted by Guido Wachsmuth on 22 January 2014 at 16:38

On 22 January 2014 at 20:06 Gabriël Konat commented:

On the fly filtering might be required for the short-circuiting ResolveDefs, since it will continue looking for definitions in other scopes if the definitions are filtered by a property.

On 20 May 2014 at 23:58 Guido Wachsmuth commented:

Is on the fly filtering still needed with disambiguation clauses?

On 21 May 2014 at 16:17 Gabriël Konat commented:

A clause like refers to Variable x of type t still requires this kind of on-the-fly filtering, but do we still need that now that we have filtering and disambiguation?

Log in to post comments