API: Rename CallExpr::operand -> CallExpr::func; *::pattern -> *::pat
#309
Conversation
This file contains 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
xFrednet
added
C-enhancement
|
Good call, I forgot about that. Thanks! |
Merged
via the queue into
rust-marker:master
with commit Nov 14, 2023
6a4bb90
22 of 23 checks passed
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.
Some smaller breaking changes before
v0.4.0probably best summarized by the changelog entry:CallExpr::operandtoCallExpr::funcRefPat::pattern()->RefPat::pat()OrPat::patterns()->RefPat::pats()Yeah, and that's it :D
I also moved the semver check higher in our CI file. I thought about making it the first item, but I feel like the others are still more important and should be the first visible CI checks. Having semver higher up is already a nice change :)
Closes #297
Closes #295