changed import to use brackets <> for openssl #907
Merged
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
real-or-random
approved these changes
Mar 21, 2021
There was a problem hiding this comment.
ACK 4504472
Indeed, it doesn't matter here but it's cleaner to use the foo <foo> syntax in this case, and I don't think there there was a specific reason to use "foo".
|
Right! Standards make it easier to understand what’s going on. |
jonasnick
reviewed
Mar 26, 2021
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.
Changes:
OpenSSL imports were changed to use angle brackets for standardization. Typically
#import <foo>is used for system and or 3rd party imports, rather than the local#import "bar".Tests:
Ran on Ubuntu 20.04 fine after building with
./configure --enable-openssl-tests. Exhaustive and other flags were ran, as well as "make check".