http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49022
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jwakely.gcc at gmail dot
| |com
--- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-05-17
14:48:35 UTC ---
To expand: *if* the '+' itself is allowed per the specs to return something !=
std::valarray, and the specs only mandate std::begin and std::end overloads
taking std::valarray& and const std::valarray& I don't see where is the bug in
our implementation. Maybe a QoI issue? I'm not sure. Admittedly I haven't
followed the recent discussion about ranges in any detail, I may be missing
something.
