You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<compare> is (equivalently) required to be included by <iterator>, and <iterator> is required to be included by <ranges>, so it seems that the synopsis of <ranges> doesn't need to show #include <compare>.
The text was updated successfully, but these errors were encountered:
We explicitly say that <compare> is included in every header that needs it, so it's clear that the comparisons using it (and other comparisons using those) are well-formed.
I see no reason to "optimize" that by removing it where it's already implicitly included. What benefit would it have? It wouldn't make anything clearer.
Implementations are free to not re-include it unnecessarily, the difference is not observable.
We explicitly say that <compare> is included in every header that needs it, so it's clear that the comparisons using it (and other comparisons using those) are well-formed.
Thank you. I think this is a clear reason to me that we should not remove #include <compare> even if it is redundant.
<compare>
is (equivalently) required to be included by<iterator>
, and<iterator>
is required to be included by<ranges>
, so it seems that the synopsis of<ranges>
doesn't need to show#include <compare>
.The text was updated successfully, but these errors were encountered: