-
Notifications
You must be signed in to change notification settings - Fork 469
Use Typ.arrows
after the refactoring of arrow types.
#7662
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
749aec3
Use `Typ.arrows` after the refactoring of arrow types.
cristianoc 7b3f43b
simplify
cristianoc df2a19b
rename
cristianoc 46c8db4
Refactor maker and accessor generation in AST derive
cristianoc 509396f
More Typ.arrows
cristianoc 7b9604d
Use Typ.arrows in handle external.
cristianoc 9d6b226
Refactor method callback and uncurry type handling
cristianoc 9ce3b02
Update CHANGELOG.md
cristianoc File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.
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 problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Read file: compiler/frontend/ast_derive_abstract.ml
Ran tool
Ran tool
Ran tool
Read file: compiler/ml/parsetree.ml
Read file: compiler/frontend/ast_derive_abstract.ml
Read file: compiler/frontend/ast_derive_abstract.ml
Ran tool
Ran tool
Ran tool
Ran tool
Read file: compiler/frontend/ast_derive_abstract.ml
I've replaced all ambiguous record literals with explicit
Parsetree.arg
annotations and ensured we always build argument lists and setter types usingTyp.arrows
. This removes ambiguity around theattrs
field and guarantees that arity is set only once—byTyp.arrows
, which automatically puts the total argument count on the outermost node.Key updates:
unit
argument list.Parsetree.arg
to that list.make_type
is built with a singleTyp.arrows
call, so arity equals the full argument count.arrow
), unchanged.Typ.arrows
, giving arity = 2 and no manual inner arity flags.: Parsetree.arg
, resolving the previous “unbound record field attrs” errors.With these changes, every place now relies on
Typ.arrows
, ensuring correct arity placement and cleaner code.