Vector exception safety

[jxy-s]

Description of the feature, modification, idea, or suggestion.

Vector is currently not fully exception safe:

radiant-cpp/radiant/Vector.h

Lines 47 to 65 in e32b683

	//
	// TODO - rad::Vector does not yet support types that might throw exceptions
	// when manipulating it. It is the intention of the radiant authors for the
	// library to be exception free. Radiant will never throw an exception
	// itself, rather it will communicate errors by returning a Result. However,
	// the radiant containers may be used with types that do not adhere to this
	// philosophy. For rad::Vector to comply to this, it must cleanly handle
	// cases where an exception interjects manipulation of it. If an exception
	// happens rad::Vector should be in the state prior to the call to
	// manipulate it. In other words, an exception occurring when manipulating
	// rad::Vector should not leave it in a partially-manipulated state. This
	// does not mean it should swallow the exception internally and return an
	// error. The exception should propagate from rad::Vector but rad::Vector
	// itself should be in a valid state when this happens.
	//
	RAD_S_ASSERTMSG((IsNoThrowDtor<T> && IsNoThrowDefaultCtor<T> &&
	IsNoThrowCopyCtor<T> && IsNoThrowMoveCtor<T> &&
	IsNoThrowCopyAssign<T> && IsNoThrowMoveAssign<T>),
	"rad::Vector does not yet support types that might throw.");

Proposed implementation details (optional)

All paths in Vector should be exception safe.

[jxy-s]

Done by: #27