Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: nknikita at niisi dot ras.ru
Target Milestone: ---
Well, it seems that there some problems with noexcept specification of
associative and unordered containers' move constructors and move assignment
oper
: unassigned at gcc dot gnu.org
Reporter: nknikita at niisi dot ras.ru
Target Milestone: ---
An example from ISO/IEC 14882:2017 (E) [class.member.lookup]/7:
struct A { int x; };// S(x,A) = {{A::x},{A}}
struct B { float x; }; // S(x,B
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89452
--- Comment #6 from Baykov Nikita ---
There is one more issue.
ISO/IEC 14882:2017(E) and N4800 specify that seekpos(sp, which) and
seekoff(off_type(sp), ios_base::beg, which) should be equivalent, but it seems
that they are not equivalent in lib
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89452
--- Comment #5 from Baykov Nikita ---
I apologize for my careless mistake.
I have some other questions that I would like to clarify. Hope it will be right
to do it here.
1. You mentioned that pptr() was no longer required to be null pointer in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89452
--- Comment #4 from Baykov Nikita ---
I apologize for my careless mistake.
I have some other questions that I would like to clarify. Hope it will be right
to do it here.
1. You mentioned that pptr() was no longer required to be null pointer in
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: nknikita at niisi dot ras.ru
Target Milestone: ---
It seems that basic_stringbuf::seekoff and basic_stringbuf::seekpos
implementations are inconsistent with the requirements
