Skip to content

Resolution Design #27

@NalaGinrut

Description

@NalaGinrut

I think it's better to separate type and name resolution, fortunately, if we do it now, it's just a little change. Here're the steps:

  1. Create Resolution class inherited from AST::ASTVisitor, and move static bool ResolveNamesAndTypes into it.
  2. Separate TypeResolution and NameResolution class inherited from Resolution class.
  3. Put them in different files.

This is better for maintenance and working parallelly.
And the name resolution will distinct names from different namespaces, like values, macros, so it's an important prerequisite for the rest of the work.

If it's OK, then I can raise PR for it.

What do you think? @philberty @SimplyTheOther

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions