https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116399
--- Comment #15 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to 康桓瑋 from comment #13) > I'm not sure it's reasonable or trivial for alias_view to be sized_range, I don't think it is necessary. Is there a use case for needing to know how many aliases there are, where ranges::distance isn't sufficient? What code would you write differently? > If it's trivial to make it satisfy sized_range, then perhaps we should > submit to the LWG to require it. It would require inspecting the aliases on construction, and then storing the size (or the end iterator). That would mean std::text_encoding::aliases() is not O(1). Why would it be an improvement?
