User talk:T. Canens/Kona17

here do we put global library wording again
I think the pages most cppreference users land on are individual functions and classes (and headers, which I find weird) - the things people find by typing stuff on google or link to from forums. So blanket wordings aren't discoverable when put on their own page.

For example, I've put the blanket wording for data races into cpp/container (even though it applies elsewhere) thinking that place is more visible than a dedicated page, but I don't think it works that well: if someone is looking up vector.insert, they have no reason to go up to containers. cplusplus.com/reference put a "Data races" section on every page (e.g. vector::insert] ) and I think that was the better decision.

For another example, there are some blanket library wording (moved-from state and xvalue aliasing) that are here in where people can (and do!) run into them, even though they apply elsewhere as well.

But for something like LWG 2795 here, I can't even think of a discoverable place. Maybe under cpp/language/adl next to where it talks about the using std::swap idiom? --Cubbi (talk) 14:14, 30 March 2017 (PDT)
 * Yes, global library wording is tricky. For something like container data races, we can probably put a link on every page as a middle-ground. But for things like LWG 2795 and 2866, which is more like "implementers mustn't be crazy", it's trickier. Maybe people take that for granted anyway and there's no real need to document them? That's the approach I think I'm going to take with 2866. T. Canens (talk) 23:10, 30 March 2017 (PDT)