Feat(semantic): implementar travessia semântica #121
Merged
Conversation
7 tasks
This was referenced Jun 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contexto
As issues de tabela de símbolos e checagem de tipos já definem as bases do analisador semântico, mas ainda faltava a infraestrutura de travessia da AST que conecta essas peças.
O analisador semântico agora percorre a AST de forma sistemática, de
ProgramatéExpr, mantendo estado de escopo, tipo de retorno da função corrente e diagnósticos acumulados durante a análise.O que foi feito
Validação
Observações
Essa etapa fecha a ponte entre o parser e as regras semânticas, preparando o projeto para evoluções mais completas de verificação de tipos e uso de símbolos.