Prepare the future analyzer #182
Draft
Conversation
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
Override-6
force-pushed
the
future/analyzer
branch
from
3888afd to
0cbcd18
Compare
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.
With the experience of a first version, the time has come to build a more resilient code analyzer that would welcome new features along the way.
Most notably, the analyzer now uses the parser instead of custom wrappers, and creates an output that is more pleasant for the compiler. IO types may still be used outside a regular file system. The compiler is still the sole component in charge of memory layouts.
Not all tests pass, especially those that heavily relies on custom behavior, such as implicit type conversions, std command aliases and structures. Various parts may be re-arranged if something better fit the purpose, especially for import directive handlers, methods and intrinsics.
The database of the analyzer is global to all reefs and shares globally some values such as types and schemas. It rethinks everything around different vectors spilled in order to avoid fighting the borrow checker by partitioning mutable accesses.
TypeRefis removed thanks to the global vector indexed byTypeIds.