feat: Identify closed runtime custody hold boundaries #101
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-cstd!101
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/runtime-custody-hold-diagnostics"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Identify original runtime hold callsites and Cargo evidence observation/retirement stages using closed literal categories. Retain original owners, raw failures and independent cleanup errors without printing exception representations, paths, tokens or identifiers.
Diagnostics capture the actual failing boundary; they do not establish its cause or successful retirement. Original native holds, deadlines and acceptance requirements remain unchanged.
The wide-string core rejection now accepts both GNU and LLVM diagnostic spelling while requiring the exact nineteen missing aliases and rejecting warnings. This retains the actual failed-link and cleanup checks instead of treating any linker error as success. The startup source oracle also includes its existing inert-by-default thread dependency and explicit feature edges. Published in
4b062cd1.The corrected wide-string rejection let CI reach the span probe, where rustc could not load the C runtime’s transitive thread ABI dependency. Routed all full-runtime Rust probes through the same retained dependency owner as their library in
7ec60da5. Withdrawal now refuses before compiler invocation, while the original extern metadata, dependency outputs and fresh-result checks remain owned throughout each call.CI now reaches the freestanding error callback, where the debug build emits an out-of-line libcore slice-method call for is_empty. Selected the same intrinsic length match already used by #111 in
dc866c7e. The known/unknown error cases and short-copy capacity assertions remain unchanged; this witness still links without a libcore implementation.