feat(parser): implement parse_cast_type function and organize module structure#91
Merged
Merged
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
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.
This pull request refactors the implementation of the
parse_cast_typefunction in the parser. The main change is moving the function from theexpressions::prefixmodule to a newtypesmodule, which improves code organization and separation of concerns. There are no changes to the logic of the function itself.Parser code organization:
parse_cast_typefunction fromsrc/parser/rules/expressions/prefix.rsto a new module,src/parser/rules/types.rs, to better separate type parsing logic from expression parsing. [1] [2] [3] [4]typesmodule to the parser rules by updatingsrc/parser/rules/mod.rs.