In some cases editor resolve works fine in the editor but it fails in SPT.

editor-resolve:
	(node, position, ast, path, project-path) -> definition
	where
		node' := <try(resolve-child)>node;
		definition := <_analysis-resolve(|<_language>, project-path)> node'

resolve-child: LHSEdgeName(name, type) -> type

Specifically when LHSEdgeName(None(), "asdf"{Use(...)}) this happens.
Without resolve-child editor resolve will try to resolve None() or anything else in the first position which might also be a definition.
But with resolve-child the second child takes precedence over the first child, at least in editor behaviour.

Submitted by Daco Harkes on 1 April 2015 at 17:02