I'm not an editor, but I play one on TV. I think this falls just short of editorial. Obviously the Editors can investigate the code and quickly determine that it's trivial to implement these functions in a way that cannot emit exceptions, but noexcept is effectively a declaration that WG21 will never change this function in a way that would require an implementation that might emit exceptions. That level of commitment to maintaining noexcept in the future is not something editors can decide trivially, but a question for the experts in LWG.

(That said I would personally appreciate such an LWG issue since I wouldn't have to find time to file it myself 😉)

LWG3533 did not endeavor to add or remove noexcept, so the issue is not related.

As @CaseyCarter explained, adding noexcept to a function that didn't have it before without showing a paper trail that clearly establishes editorial error is not an editorial issue. Please file an LWG issue if you feel a change is warranted in that area.

but noexcept is effectively a declaration that WG21 will never change this function in a way that would require an implementation that might emit exceptions.

@CaseyCarter. Do you mean that even for lazy_split_view​::​outer-iterator​::​value_type::end() which only returns default_sentinel, adding a noexcept for it is still worth an LWG issue?

I tried to combine this end() with the above base() const &s into a single LWG, but it seems more worthy of being independent.

@CaseyCarter. Do you mean that even for lazy_split_view​::​outer-iterator​::​value_type::end() which only returns default_sentinel, adding a noexcept for it is still worth an LWG issue?

Yes - that's not an editorial change.

I tried to combine this end() with the above base() const &s into a single LWG, but it seems more worthy of being independent.

I'd file these as distinct issues: ideally you want an LWG issue to be as small and simple as possible so it's a no-brainer for folks to say "yes, this is an issue and the resolution is obviously correct." Doing so enables LWG to avoid lots of heavy process, making it more likely your resolution will be applied sooner rather than later.