https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86135
--- Comment #12 from Sabetay Toros ---
Created attachment 44272
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44272=edit
Testi case for crashed initialiazer list
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86135
--- Comment #11 from Sabetay Toros ---
Here is my test case. The issue is in line 30. Please change the line
commented with direct initilization.
It wont crash.
If you are right list initializers is not usable.
I hope you have an answer.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86135
--- Comment #9 from Sabetay Toros ---
I´ve examined your link. This is not the same case as you are stating. I am
not initializing a vector with an initializer list, rather I am trying to
initialize only one object member with a universal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86135
--- Comment #6 from Sabetay Toros ---
Hi,
*Because the rules for direct-initialization (with parentheses)
andlist-initialization (with braces) are different. Different rules
meansdifferent things happen. *
the rules may be different but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86135
--- Comment #4 from Sabetay Toros ---
*" --- Comment #2 from Jonathan Wakely http://gnu.org/>> ---This is not a bug, GCC is correct. With
list-initialization the compiler doesnot always select a copy/move
constructor even when the argument is
Reporter: sabetaytoros at gmail dot com
Target Milestone: ---
Operating System Windows 8.
Compiler On internet wandbox.org gcc HEAD 9.0 2018O6
$ g++ prog.cc -Wall -Wextra -I/opt/wandbox/boost-1.67.0/gcc-head/include
-std=gnu++2a
Issue :
Initializing an element with angel brackets does