While our type traits are named is_nothrow_something, we also have NoThrowForwardIterator (note capital F, indicate a new word).

If we fix this, we should remove the hyphen from "no-throw" (names of exposition-only concepts) and we should rename NoThrowForwardIterator to NothrowForwardIterator for consistency.

@jwakely: Thoughts? We're inclined to drop the hyphen and say "nothrow" everywhere.

I think making nothrow-sentinel-for consistent with nothrow_constructible makes sense. I'm less convinced that NothrowFoo is an improvement on NoThrowFoo.

Right, I'd also be happy with keeping the camel-case "NoThrow", that seems inoffensive enough. @jensmaurer: could you live with "nothrow-foo" and "NoThrowFoo"?

I'm ok with that; it's an incremental improvement which we can iterate on in the future should the pain about NoThrowFoo grow.

Great, let's do that then: snake-case nothrow_foo without hypen, and camel-case can use NoThrowFoo is desired.