-
Notifications
You must be signed in to change notification settings - Fork 142
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
Brace constructing a toml::value inserts a new array element in GCC 10.2.1 #165
Comments
MartinHelmut
added a commit
to krieselreihe/litr
that referenced
this issue
Mar 31, 2022
This is currently a workaround to mitigate an issue in Toml11: ToruNiina/toml11#165
MartinHelmut
added a commit
to krieselreihe/litr
that referenced
this issue
Mar 31, 2022
This is currently a workaround to mitigate an issue in Toml11: ToruNiina/toml11#165
MartinHelmut
added a commit
to krieselreihe/litr
that referenced
this issue
Mar 31, 2022
This is currently a workaround to mitigate an issue in Toml11: ToruNiina/toml11#165
I am also having this issue |
This is really not a nice problem to run into when initializing a class member with the result of struct config_file {
explicit config_file(const char* filename) : root_{toml::parse(filename)} {}
const toml::value root_;
}; results in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
toml11v3.7.0
The
toml2
variable in the below example is copy constructed incorrectly and has an empty array inserted on GCC but is correctly constructed on clang. The error looks to be to do with thetoml::value
std::intializer_list
constructorstd::enable_if
being too broad (toml/value.hpp:840).The text was updated successfully, but these errors were encountered: