[Bug libstdc++/120305] Cannot create a std::vector from a std::ranges::transform_view.

2025-05-17 Thread aneris at disroot dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120305 --- Comment #17 from aneris --- Alright, I understand. Thank you again.

[Bug libstdc++/120305] Cannot create a std::vector from a std::ranges::transform_view.

2025-05-17 Thread aneris at disroot dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120305 --- Comment #15 from aneris --- (In reply to aneris from comment #14) > (In reply to aneris from comment #13) > So I was wondering, is it really out of the question to promote __int128_t to > an integer type by default like Clang? It'd make so

[Bug libstdc++/120305] Cannot create a std::vector from a std::ranges::transform_view.

2025-05-17 Thread aneris at disroot dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120305 --- Comment #14 from aneris --- (In reply to aneris from comment #13) > I did some digging and this is because std::is_integral_v<__int128_t> is > unconditionally true in libc++, unlike in libstdc++ where it's only true > when the GNU extension

[Bug libstdc++/120305] Cannot create a std::vector from a std::ranges::transform_view.

2025-05-17 Thread aneris at disroot dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120305 --- Comment #13 from aneris --- (In reply to Jonathan Wakely from comment #12) > tl;dr if you want to compile with strict -std=c++20 -pedantic settings, you > need to strictly follow the rules of the standard. I understand, though, at the very

[Bug libstdc++/120305] Cannot create a std::vector from a std::ranges::transform_view.

2025-05-16 Thread aneris at disroot dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120305 --- Comment #9 from aneris --- Hmm, alright. Thank you very much for your time.

[Bug libstdc++/120305] Cannot create a std::vector from a std::ranges::transform_view.

2025-05-16 Thread aneris at disroot dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120305 --- Comment #3 from aneris --- (In reply to Andrew Pinski from comment #2) > The difference is int128_t support. Could you elaborate a bit? I am afraid I don't follow.

[Bug libstdc++/120305] Cannot create a std::vector from a std::ranges::transform_view.

2025-05-16 Thread aneris at disroot dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120305 --- Comment #5 from aneris --- (In reply to Andrew Pinski from comment #4) > (In reply to aneris from comment #3) > > (In reply to Andrew Pinski from comment #2) > > > The difference is int128_t support. > > > > Could you elaborate a bit? I am

[Bug libstdc++/120305] Cannot create a std::vector from a std::ranges::transform_view.

2025-05-16 Thread aneris at disroot dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120305 aneris changed: What|Removed |Added CC||aneris at disroot dot org --- Comment #1 from

[Bug libstdc++/120305] New: Cannot create a std::vector from a std::ranges::transform_view.

2025-05-16 Thread aneris at disroot dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120305 Bug ID: 120305 Summary: Cannot create a std::vector from a std::ranges::transform_view. Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal