[libcxx-commits] [PATCH] D106763: [libc++][RFC] Disable incomplete library features.

[Mark de Wever via Phabricator via libcxx-commits]

Mordante added a comment.

Yes we can do the same for ranges.
I think that partly boils down to what kind of errors we want to give the user, a clear diagnostic explaining how to opt-in to the feature.
Or a less clear message due to a not implemented algorithm.
I know there are some ABI breaking ranges papers retroactively accepted in the June plenary, I don't know whether these ABI breaking changes will affect libc++.

@cjdb @zoecarver is our ranges implementation in main affected by the ABI breaking papers accepted in the June plenary?


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D106763/new/

https://reviews.llvm.org/D106763