Make Addressable rustdoc teach complete workflows - #2
Merged
Conversation
Dynamic guards require the space and revision that produced their observed value. Returning only the subject and value forced dynamic callers to reach through ReferenceTool into Basilica. Carry that context in DynamicExplanation so tooling can construct a guarded transaction using only the dynamic boundary.
Explain who constructs or receives each pivotal type, where its evidence comes from, and which operation consumes it. Reserve doctests for real workflows and static laws, and keep isolated constructor invariants in unit tests. Reshape the executable tour into five narrated chapters while retaining its semantic assertions.
waywardmonkeys
force-pushed
the
codex/rustdoc-workflows
branch
from
August 24, 2026 18:35
9b6e657 to
41ca04b
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
1 participant
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.
This follow-up makes Addressable's public documentation navigable from both crate-level workflows and individual type pages.