TODOs:

• refactor the API to use iterators all the way to the consumer
  • this allows aborting analysis if no more information is needed
  • API user can decide whether to use potentially shadowed uses
• add tests
• look for possible performance optimizations
  • this is optional as the cache already saves quite a bit of redundant work
  • but still generators are pretty slow

More things to consider for final API design:

• should be able to modify scopes by adding removing declarations
  • should only work on a forked Resolver to not interfere with other users of that Resolver
• should be able to get a Symbol by name (e.g. arguments)
  • probably requires direct access to Scope (would also simplify the previous bullet point)
• needs a way to distinguish the following cases
  • implicitly available identifier (arguments)
  • identifier from merged declaration (namespace and enum)
  • no declaration found

If possible it should also track this and super. These are treated as identifiers without declaration like arguments. That means we also need to look for this and super keywords.
In addition this lives in the type and value domain.