Runtime & Errors

Runtime & Errors

Part of the Sun ABI draft. These are proposed requirements, not guarantees of current releases. Open decisions must be resolved before stabilization.

Runtime, errors, and global state

Suppose two libraries share a registry:

app → left  → registry
app → right → the same registry

The registry must initialize once, before either consumer uses it. Linking two copies of runtime code must not accidentally create two instances of state whose contract says it is process-wide.

For errors, imagine a library throwing while the caller owns a file. Both sides must agree how the error crosses the call and how the file is cleaned up. An unwinding mechanism that skips that cleanup is not compatible.

Runtime requirements are part of the single bundle contract. Adding a runtime service does not affect bundles that do not call it. A runtime implementation can be refactored or optimized while preserving its existing interface and behavior. An incompatible change needs a distinct service identity or an adapter that implements the old behavior during its supported lifetime.

Minimal exampleLevelRequirement
A compiled function calls an allocation service.MUSTInclude the runtime interfaces actually required by compiled code in the bundle contract, covering argument and result representations, ownership, and failure behavior.
That service changes the meaning of its size argument.MUST NOTChange the calling rules or specified behavior of an existing runtime service identity. Use a distinct identity for incompatible behavior.
An adapter translates an old call into the current allocator call.SHOULDReuse the current runtime implementation or a small adapter when it can satisfy an older supported interface.
Two incompatible services export the same linker symbol.MUST NOTSilently select an incompatible implementation when bundles use the same runtime symbol.
A library throws an error that the caller catches.MUSTDefine exception objects, type identification, matching, cleanup, and unwinding.
An error crosses a frame holding an owned file.MUSTAllow unwinding across a boundary only when both sides support its contract.
The caller does not understand the library error representation.MUSTSpecify throwing and catching across bundles, or explicitly reject unsupported throwing boundaries.
Both left and right imports reach one shared counter.MUSTInitialize dependencies before consumers and each deduplicated global instance exactly once.
A thread exits while it owns library thread-local values.MUSTDefine shutdown order, initialization failure, thread-local state, and state shared among bundles.
Two embedded runtimes must not create two supposedly global registries.MUST NOTDuplicate state defined as process-wide when bundling several runtime implementations.

Open decisions

List emitted runtime symbols and specify exception machinery, type-ID collision handling, startup, teardown, and thread-local storage.