Skip to content

docs(dynamic_allowlist): document merge, read, insert, remove, and shared - #4906

Closed
0x5t4l1n wants to merge 1 commit into
NVIDIA:mainfrom
0x5t4l1n:docs/dynamic-allowlist-merge
Closed

0x5t4l1n wants to merge 1 commit into
NVIDIA:mainfrom
0x5t4l1n:docs/dynamic-allowlist-merge

Conversation

@0x5t4l1n

Copy link
Copy Markdown

Summary

Five public methods on DynamicStringAllowlist had no doc comments while
all their neighbours were fully documented:

Method Before After
merge no doc documents that it does not mark synced (unlike replace)
read no doc explains the lock guard lifetime
insert no doc notes no-sync side-effect, consistent with merge
remove no doc one-line description
shared no doc explains the Arc clone

The most important gap is merge: callers that use merge to populate the
allowlist incrementally must call mark_synced themselves afterwards, or
wait_synced / is_synced will never report true. Without a doc
comment this invariant is invisible.

No behaviour is changed; this is documentation only.

Test plan

  • cargo doc -p openshell-core --no-deps — rendered docs look correct
  • cargo test -p openshell-core — no regressions

🤖 Generated with Claude Code

…ared

The public methods merge, read, insert, remove, and shared lacked doc
comments, while their neighbours (new, from_set, replace, mark_synced,
is_synced, wait_synced) were all documented.

The most important gap is merge: unlike replace it does not mark the
allowlist as synced, which is a subtle invariant that callers must observe
to avoid wait_synced timing out forever. The new doc comment calls this
out explicitly and refers to mark_synced so readers know what to call
after consuming the authoritative source.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@copy-pr-bot

copy-pr-bot Bot commented Oct 24, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@github-actions

Copy link
Copy Markdown

Thank you for your submission! We ask that you sign our Developer Certificate of Origin before we can accept your contribution. You can sign the DCO by adding a comment below using this text:


I have read the DCO document and I hereby sign the DCO.


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the DCO Assistant Lite bot.

@github-actions

Copy link
Copy Markdown

Thank you for your interest in contributing to OpenShell, @0x5t4l1n.

This project uses a vouch system for first-time contributors. Before submitting a pull request, you need to be vouched by a maintainer.

To get vouched:

  1. Open a Vouch Request discussion.
  2. Describe what you want to change and why.
  3. Write in your own words — do not have an AI generate the request.
  4. A maintainer will comment /vouch if approved.
  5. Once vouched, open a new PR (preferred) or reopen this one after a few minutes.

See CONTRIBUTING.md for details.

@github-actions github-actions Bot closed this Oct 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant