CS fixes: always use parentheses when instantiating a class#201
Merged
antecedent merged 1 commit intomasterfrom Mar 30, 2026
Merged
CS fixes: always use parentheses when instantiating a class#201antecedent merged 1 commit intomasterfrom
antecedent merged 1 commit intomasterfrom
Conversation
Includes selectively applying this to a few of the test fixtures to make them more syntax-varied without affecting their function.
Collaborator
Author
|
@antecedent P.S.: would you mind turning on auto-branch-delete on merge ? Should be on the Settings "homepage": |
antecedent
approved these changes
Mar 30, 2026
Owner
|
@jrfnl Thank you for the initiative with the code style changes! I just changed the setting to auto-delete head branches. |
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
2 participants
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.
Preliminary PR to unblock introducing code style rules as discussed in #180 (comment) (and follow-up comments).
Includes selectively applying this to a few of the test fixtures to make them more syntax-varied without affecting their function.