On Sun, 1 Dec 2024 at 19:00, Sebastian Wittmeier via Std-Proposals <std-proposals@lists.isocpp.org> wrote:Would it be affected by the design decision of retiring niebloids?
P3136
No, because what Avi showed below is not a niebloid, it's just a function object. Niebloids are the strange "might be a magical function template or it might not be" things previously used for specifying constrained algos such as std::ranges::copy. What has been retired is the "maybe a function template and maybe not" property. Using function objects (or customization point objects) to implement operations such as "swap" or "copy" or Avi's proposed "construct" has not been retired.