[expected.general] Contradictory description of expected<T, E>.

[cassioneri]

Paragraph 1 states (emphasis added):

[...] An expected<T, E> object holds an object of type T or an object of type unexpected<E> [...]

which contradicts [expected.object.general]/1 which says (emphasis added):

Any object of type expected<T, E> either contains a value of type T or a value of type E within its own storage.

The description in [expected.general] is a leftover from the original proposal which was simplified during LWG review. The description in [expected.object.general] was fixed accordingly but the one in [expected.general] was missed.

@jwakely and @Dani-Hub might confirm.

[jwakely]

Yes, the exposition-only member was originally unexpected<E> but we changed it to just E and must have missed this part.

[frederick-vs-ja]

This should have been fixed.

This issue can be automatically closed if you had written Fix #6714 in the PR description.

(quoting from MSVC STL's good-first-issues):

You can (and should) link your pull request to this issue using GitHub's close/fix/resolve syntax.
(in the PR description not the commit message)