On 1 June 2017 at 18:29, Jonathan Wakely <jwak...@redhat.com> wrote: >> They all seem to be shortcuts for something::value, so it seems to me >> logical to have >> them all be _v. > > > The _v suffixes in the standard are there to distinguish std::foo from > std::foo_v, but we don't have that problem.
Wouldn't necessarily hurt to follow the same naming convention idea as the standard, but sure, we don't have that problem, agreed.