https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103831
Patrick Palka changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103831
--- Comment #5 from Patrick Palka ---
(In reply to 康桓瑋 from comment #2)
> Please let me add a digression, is the standard overconstrained the
> definition of tiny_range?
> In the current standard, it seems that only single_view and empty_view
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103831
--- Comment #4 from CVS Commits ---
The releases/gcc-11 branch has been updated by Patrick Palka
:
https://gcc.gnu.org/g:614a9580d4463c4aefd74c40ed46bfab2bef65c7
commit r11-9456-g614a9580d4463c4aefd74c40ed46bfab2bef65c7
Author: Patrick Palka
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103831
--- Comment #3 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:0378f563b0321c44c4a9c98cf46d2a22b9160f76
commit r12-6485-g0378f563b0321c44c4a9c98cf46d2a22b9160f76
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103831
--- Comment #2 from 康桓瑋 ---
Please let me add a digression, is the standard overconstrained the definition
of tiny_range?
In the current standard, it seems that only single_view and empty_view satisfy
tiny_range. However, std::array and span