format using black #15
Closed
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
Use 79 columns as when resolving conflicts using 3-way diff view, 80 columns per diff already requires a lot of screen-estate... Signed-off-by: Hubert Kario <hkario@redhat.com>
|
I have just refactored everything to put Kyber specific functions into new classes, so maybe the easiest thing to do is close this is to rebase from main and run black again? I'm sorry but I figured black reformatting was easier than merging this and then doing the conflicts on code changes |
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.
Use 79 columns as when resolving conflicts using 3-way diff view, 80 columns per diff already requires a lot of screen-estate...