Nothrow Requirements
status: draft
security: NO
safety: ASIL_B

Requirements#

Nothrow allocation failure signaling
status: invalid
security: NO
safety: ASIL_B
reqtype: Functional

The score::nothrow memory-resource allocation interfaces shall not throw on allocation failure and shall instead signal failure by returning nullptr.

Nothrow fallible construction
status: invalid
security: NO
safety: ASIL_B
reqtype: Functional

Containers in score::nothrow shall provide explicit fallible factory functions that return score::Result<Container> for construction paths that may require allocation.

Nothrow explicit mutation error propagation
status: invalid
security: NO
safety: ASIL_B
reqtype: Functional

Container operations that may allocate during mutation shall provide explicit error-propagating APIs using score::Result or score::ResultBlank instead of relying on exception-based failure signaling.

Nothrow aborting convenience operations
status: invalid
security: NO
safety: ASIL_B
reqtype: Functional

For operations with explicit error-propagating APIs, score::nothrow shall provide clearly named OrAbort convenience variants for cases where allocation failure is considered a programming error.

Nothrow pointer-slot policy abstraction
status: invalid
security: NO
safety: ASIL_B
reqtype: Functional

score::nothrow containers shall store persisted internal pointers through a selectable pointer-slot policy abstraction so that storage semantics can be changed without rewriting the container algorithms.

Safety Impact#

Nothrow library ASIL level
status: invalid
security: NO
safety: ASIL_B
reqtype: Functional

The score::nothrow library shall be ASIL-B compliant.