[ffigen] Remove Constant from public AST - #3556
Merged
Merged
Conversation
PR HealthBreaking changes ✔️
This check can be disabled by tagging the PR with API leaks ✔️The following packages contain symbols visible in the public API, but not exported by the library. Export these symbols or remove them from your publicly visible API.
This check can be disabled by tagging the PR with Changelog Entry ✔️
Changes to files need to be accounted for in their respective changelogs. This check can be disabled by tagging the PR with |
liamappelbe
marked this pull request as ready for review
August 17, 2026 04:15
Constant from public ASTConstant from public AST
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.
Constantis used as the base class ofUnnamedEnumConstantandMacroConstant. But it's also used inparseVarDeclaration, when we want to codegen the parsed variable as a Dart constant instead of aGlobal. This pollutes the public AST with internal details.Constantshould not be part of the public AST at all.aBeyond that API issue, it's also a problem for the visitor config migration because part of that constness decision is checking
config.globals.includeSymbolAddressat parse time (if a user wants the symbol address, we need to treat it as aGlobalinstead of aConstant). We want to move that config field to a visitor, so this refactor changesparseVarDeclarationto always return aGlobal. If the variable has a constant value, we store it on theGlobal. That lets us defer the decision about how to codegen it.Generally this simplifies things, but it slightly complicates the
Libraryconstructor's decision about whether a binding belongs inlookupBindingsornoLookupBindings, since aGlobalis aLookupBindingin the class hierarchy, but doesn't actually look anything up ifisConst.ConstantValue.typemirrorsConstant.rawType. It would be nice if we could use the type of the enclosingGlobal. But it's not that simple because, for example,const char*Globals are codegenned asPointer<Char>, but we want to codegen theConstantValueasString.