Avoid using complex number literal extension.#18
Merged
Conversation
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
1 participant
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.
Previously, I used the complex number literal compiler extension to build complex numbers as well as extract their real and imaginary parts. (e.g.
double _Complex = 2 + 1jto build the number2 + i.)This was nice because it avoided using
<complex.h>as well as C++'s<complex>. However, not all compilers support these extensions by default. (You need to use-std=gnu++20instead of-std=c++20.)This PR modifies the repo to no longer use these literals, instead relying on the C specification's guaranteed memory layout for complex numbers.