refactor(fspy-shm): expose explicit backing-file removal - #642
Draft
wan9chi wants to merge 1 commit into
Draft
Conversation
fspy benchmarklinuxmacoswindows |
wan9chi
force-pushed
the
feat/fspy-shm-sigsafe-unlink
branch
2 times, most recently
from
August 11, 2026 03:25
cd36e35 to
f578304
Compare
wan9chi
force-pushed
the
feat/fspy-shm-sigsafe-unlink
branch
from
August 11, 2026 04:24
f578304 to
c1f27ca
Compare
Co-authored-by: GPT-5 Codex <[email protected]>
wan9chi
force-pushed
the
feat/fspy-shm-sigsafe-unlink
branch
from
August 11, 2026 05:14
c1f27ca to
ec93753
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Callers already retain the full shared-memory backing path, so ShmKeeper duplicated path ownership and hid cleanup failures behind Drop. Return the handle directly and expose a fallible remove operation instead, making backing-file lifetime explicit and keeping the eventual injected-runtime API borrowed and allocation-free.