timsong-cpp
timsong-cpp
_Requires:_ clauses in the standard and the concepts `requires` constraints are different beasts. Breaking a _Requires:_ clause results in undefined behavior unless otherwise specified; not satisfying a constraint means that...
> I don't think the standard is particularly consistent about how it denotes what would be used as concepts constraints. For example, swap (20.2.2) in the C++17 draft standard has:...
This can split an entity into several, though. Consider: struct foo_fn { // \requires XXXX template void operator()(const A&, const B&) const; // \requires YYYY // \returns ZZZZ template int...
> The function object and the functions are not equivalent. So a reference documentation shouldn't do that. I would rather have a blanket introductory paragraph explaining that they are actually...
"The standard Range TS" is a different beast because it uses this only for actual customization points, where you need to specify a complicated set of lookup rules which is...
> If this ticket don't pretend to take care of N4381-style customization point objects anymore, how would Standardese document such function objects? Actual customization point objects with complicated overload resolution...