Move Platform
class into preprocessor.py
#198
Merged
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.
There was a circular dependency between platform.py and preprocessor.py:
Platform
storesMacro
andMacroFunction
objects; andMacroExpander
requires aPlatform
.Breaking this dependency enables
Platform
arguments in preprocessor.py to be decorated with the correct type-hints. This code structure is also a better reflection of howPlatform
is used by the preprocessor.Related issues
Proposed changes
Platform
definition from platform.py to preprocessor.pyplatform.Platform
to usepreprocessor.Platform
instead.Reviewing the code, it is clear that a
Platform
doesn't really represent a "platform" in the sense we mean it elsewhere. It's really something like a "preprocessor state", and we construct a differentPlatform
for each file in a codebase. As a follow-up to this PR I intend to renamePlatform
and tidy it up, but I wanted to make sure simply moving the class didn't break anything before going further.