-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on iterator_category = int
with GCC 13
#4079
Comments
Reproducer: https://godbolt.org/z/T6n3Pv48d Fails also with other compilers. |
Fixed in de684ef, thanks for reporting. |
mtremer
pushed a commit
to ipfire/ipfire-2.x
that referenced
this issue
Aug 15, 2024
- Update from version 11.0.1 to 11.0.2 - Update of rootfile - Changelog 11.0.2 - Fixed compatibility with non-POSIX systems (fmtlib/fmt#4054, fmtlib/fmt#4060). - Fixed performance regressions when using `std::back_insert_iterator` with `fmt::format_to` (fmtlib/fmt#4070). - Fixed handling of `std::generator` and move-only iterators (fmtlib/fmt#4053, fmtlib/fmt#4057). Thanks @Arghnews. - Made `formatter<std::string_view>::parse` work with types convertible to `std::string_view` (fmtlib/fmt#4036, fmtlib/fmt#4055). Thanks @Arghnews. - Made `volatile void*` formattable (fmtlib/fmt#4049, fmtlib/fmt#4056). Thanks @Arghnews. - Made `Glib::ustring` not be confused with `std::string` (fmtlib/fmt#4052). - Made `fmt::context` iterator compatible with STL algorithms that rely on iterator category (fmtlib/fmt#4079). Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have some non-trivial code featuring C++ concepts, which eventually fails on
where
ctx
isfmt::format_context
.The relevant part of error output:
I may be able to write a minimal reproducer, but the issue seems obvious:
fmt/include/fmt/base.h
Line 1163 in bc8d32e
Changing this to
using iterator_category = std::output_iterator_tag;
fixed the errors.The text was updated successfully, but these errors were encountered: