-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uniform initialization causes problems with gcc #22
Comments
Thanks, that's interesting!
Can you make a PR ? |
Hi, |
Merged. Please close out as appropriate. |
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uniform initialization (curly braces initialization) is being used in
either.hpp
, and while there should be nothing wrong with that some compilers do not handle this well.For instance, uniform initialization causes problems with nlohmann's json library compiled with gcc, as backed with this issue: nlohmann/json#985
So, using neither with gcc and json objects causes the latter being modified.
As an excercise I have removed uniform initialization from either.hpp and after that Either wrapped around json I was playing with worked as expected.
The text was updated successfully, but these errors were encountered: