Repository navigation
Publish the v0.8.0 release and the redesigned site - #6
Merged
Merged
Conversation
The eight derive pages and their index now name Context-Generic Programming. The ExtractField page and its example module now accept a bare unit variant, whose payload is Nil, instead of claiming it needs a payload struct. Co-Authored-By: deepseek-v4.1-flash-1017
The nine component pages, the ten handler-family pages, and their two indexes now name Context-Generic Programming, and the component pages relate the tag line. Co-Authored-By: deepseek-v4.1-flash-1017
The twelve type pages now name Context-Generic Programming. Co-Authored-By: deepseek-v4.1-flash-1017
The three wiring trait pages and their index now name Context-Generic Programming, and the trait pages relate the tag line. Co-Authored-By: deepseek-v4.1-flash-1017
The fourteen field-access and shape trait pages now name Context-Generic Programming, and HasField relates the tag line. Co-Authored-By: deepseek-v4.1-flash-1017
The twelve variant and namespace trait pages now name Context-Generic Programming, and the namespace pages relate the tag line. Co-Authored-By: deepseek-v4.1-flash-1017
The HasField, ExtractField, and FromVariant pages no longer carry the tag line, which belongs to the constructs that choose an implementation. The HasField page keeps its glossary link for context. Co-Authored-By: deepseek-v4.1-flash-1017
The seventeen record-builder and optional-field pages now name Context-Generic Programming in their opening paragraphs. The `HasOptionalBuilder` page no longer says `FinalizeOptional` reports the first missing field, since it names the last unset one; the `TransformOptional` page names both ways the two transform markers differ; and the `HasBuilder` expansion shows the companion's doc line. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The thirteen casting and type-level pages now name Context-Generic Programming in their opening paragraphs. The `MapTypeRef` page no longer says the `: 'a` bound keeps the storage type from outliving the borrow, since it requires the storage to live at least that long. The `TransformMap` title gains its apostrophe, the `MapFields` notice names `BuildAndMergeOutputs` as the dispatch provider it is, and the borrowed companion's expansion shows its doc line. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The nine formatting and monad pages and the trait section's index now name Context-Generic Programming in their opening paragraphs, and the index relates the tag line to the wiring traits it introduces. The `StaticString` title gains the apostrophe in `&'static`, and the `StaticString` and `ConcatPath` pages no longer call the group three recovery traits, since `ConcatPath` composes paths rather than recovering a string. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every expansion block on the derive and trait pages now shows the doc line the derives put on each partial companion, as `cargo cgp expand` prints it. Eight trait pages used "CGP" in their generated-machinery notice, above the paragraph that first names Context-Generic Programming; the notices now say "the library". The `TransformOptional` page no longer says `TransformMapDefault` cannot apply to a field type without `Default`, since its `IsPresent` impl needs no bound. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The monad pages, `MapFields`, and `TransformMap` now link "provider" and "provider trait" to the glossary on first use. The formatting index and its line in the trait index say that two traits recover a name as runtime data and the third joins type-level paths, since `ConcatPath` computes only a type. The `CanDowncastFields` description no longer says the trait is never used on its own, which its page contradicts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The monad pages say their traits are not CGP components; that first use now links the glossary's component entry, as "provider" already does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every dispatch page's overview now names Context-Generic Programming and links the introduction, with a short form of the tag line where the page's construct chooses an implementation. The BuildAndMergeOutputs quote of the ref-component failure now matches its blessed stderr, which prints the implemented components without the crate prefix.
Each handler and monad provider page now opens with Context-Generic Programming linked to the Introduction, before any other "CGP", and most relate the pluggable-provider idea to the page's job. The handler index no longer says its parameters are all inner providers, since `UseInputDelegate` carries a dispatch table. Co-Authored-By: deepseek-v4.1-flash
Each error provider page now opens with Context-Generic Programming linked to the Introduction, before any other "CGP", and relates the pluggable provider choice to the page's job. The error index's description no longer uses the abbreviation before the full name. Co-Authored-By: deepseek-v4.1-flash
The sixteen top-level provider pages and their index now open with Context-Generic Programming linked to the Introduction, before any other "CGP", and relate the provider choice to the page's job. The index description and the legacy notice on the UseDelegate page no longer use the abbreviation first. The UseFieldRef pages also state the 'static bound on the mutable borrow. Co-Authored-By: deepseek-v4.1-flash
The &str getter reads a String field and converts it with AsRef::as_ref, so the expansion blocks and prose on the getter provider pages now match `cargo cgp expand`. Six opening sentences name the page's own choice, and the handler index says a list runs in sequence. Co-Authored-By: deepseek-v4.1-flash
The index page opened with the abbreviation and never named Context-Generic Programming, and it stated the whole tag line, which belongs on the pages that present the project. It now names the project in full in its opening, links the Introduction, and relates the short form to the comparisons. C++ policy-based design also moves to sidebar position 2, where the guide and the index table place it, so the sidebar matches the routing order.
The page opened with the abbreviation and stated the whole tag line, which belongs on the pages that present the project. Its opening now names Context-Generic Programming, links the Introduction, and relates the short form to the comparison, and its description names the project for search.
The page opened with the abbreviation, so it never introduced Context-Generic Programming to a reader who arrives from a search for "capabilities in Rust". Its opening now names the project, links the Introduction, and relates the short form, and its description names the project for search.
The page opened with the abbreviation and stated the whole tag line. Its opening now names Context-Generic Programming, links the Introduction, and relates the short form to the injection comparison, and its description names the project for search.
The page opened with the abbreviation and stated the whole tag line. Its opening now names Context-Generic Programming, links the Introduction, and relates the short form to the dispatch comparison, and its description names the project for search. The Sources entry for the MDN prototype-chain guide also pointed at a path MDN does not serve, so it now uses the same URL as the body's link.
The page opened with the abbreviation and stated the whole tag line. Its opening now names Context-Generic Programming, links the Introduction, and relates the short form to the implicit-parameter comparison, and its description names the project for search. The Scala syntax note now says that parts of the given syntax changed in 3.6 and that the original form remains accepted for now, which is what the reference says.
The page opened with the abbreviation and stated the whole tag line in a second paragraph. Its opening now names Context-Generic Programming, links the Introduction, and relates the short form to the module comparison, and its description names the project for search.
The page opened with the abbreviation and stated the whole tag line in a second paragraph. Its opening now names Context-Generic Programming, links the Introduction, and relates the short form to the policy comparison, and its description names the project for search.
The three pages put a space before a comma, period, colon, or semicolon that followed an inline code span or a link, which reads as a typo and came from an earlier reflow. The punctuation now sits against the span or link.
The page opened with the abbreviation and described the project without its name. Its opening now names Context-Generic Programming, links the Introduction, and relates the short form to the reflection comparison, and its description names the project for search. The cgp-serde source links now point at the v0.8.0 branch the page describes, and the project goal link follows its moved URL. Punctuation now sits against the code spans and links it follows.
The page opened with the abbreviation and described the project without its name. Its opening now names Context-Generic Programming, links the Introduction, and relates the short form to the row comparison, and its description names the project for search. The PureScript row quote now keeps "with duplicates", which the source states and the page's later point about scoped labels depends on, and the effect-row reason cites the purescript-eff README that carries it.
The page opened with the abbreviation and described the project without its name. Its opening now names Context-Generic Programming, links the Introduction, and relates the short form to the proposals it compares, and its description names the project for search. A duplicated word in the borrowing bullet is gone, and the spacing before closing parentheses and a full stop is fixed.
Both project indexes now add the crates from crates.io, pinned to the releases built on `cgp` 0.8.0, in place of a git dependency on the repository. Hypershell's pages say which toolchain a program needs: the library and small programs build on stable Rust, and only programs that nest others deeply need nightly with the new trait solver, so the index, the section index, the crate layout, the writing guide, and the limitations page no longer say every Hypershell crate needs nightly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every requirement on an external crate in `example-code` rises to the newest version it allows, so the snippet tests never resolve an older release than the one they ran against. Each change stays within semver compatibility, and the crate keeps no lockfile in the repository. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Release notes category covers four artifacts: `cgp-serde` and `hypershell` sub-categories follow `cgp` and `cargo-cgp`, with pages for cgp-serde v0.1.0 and v0.2.0 and Hypershell v0.1.0, each written from its tag's source. The index lists the two projects, and each project's Projects index links its notes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Both pages describe their release as shipped, with the date and the tag, compare, and crates.io links set on release day. cgp-serde v0.3.0 moves to cgp v0.8.0, renames `SerializeFields` to `SerializeRecordFields`, and adds the enum providers; Hypershell v0.2.0 replaces its presets with `HypershellNamespace`, dispatches its handlers on paths, and fixes HTTP, command, and WebSocket defects. The index names each project's newest release, and its versioning section covers both projects. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`CanDeserializeJsonString<T>` applies to a context that has an error type and can deserialize `T` through `DeserializeFromJsonString`, not to every context with an error type. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pages' openings and summaries split sentences that carried several points, the compatibility lines state each `cgp` requirement plainly, the index's paragraph on the two projects' numbering is split into sentences with one point each, and lines are rewrapped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The concept, reference, and comparison pages that used the email sender now use the Overview's storage component: `App` wires `FetchS3Object` and `TestApp` wires `FetchLocalObject`. The two shared diagrams, the example-code counterparts, and the check-traits fixtures and quoted diagnostics follow. The storage methods are synchronous, the Overview's included, so a reader new to CGP meets one idea at a time. The Overview and the consumer and provider page each say once that a real storage client would be async, and point to the storage tutorial, which keeps the async form. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The dependency-injection comparison's storage component drops its async method, as the other teaching pages did. The storage tutorial, which keeps the async form, now calls the Overview's code a synchronous version of its component, where it said the same component. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pages that use the storage example say what each context carries, what the `HasS3Client` and `HasLocalDir` bounds stand for, and which context's wiring selects a provider, and they replace a semicolon and a long appositive with sentences that state how their claims connect. The Overview's note on async matches the consumer and provider page's. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The compile-fail snapshot quotes the line of `cgp_provider` in `cgp-macro`'s `lib.rs`, which moved from 136 to 133 when cgp#302 shortened the crate's documentation. CI skips the compile-fail suite, so only a local run reported the mismatch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The docs grew since the last count, so the post's word and printed-page figures fell behind; they are recounted by the record's method. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The post now names cgp-serde 0.3.0 and Hypershell 0.2.0, which move to cgp v0.8.0 at the same time, with links to their release notes, and links the cargo-cgp v0.1.0 notes, calling the tool CGP's error toolchain. The closing concedes the small ecosystem beside the learning curve, the description leaves the agent skill to its section, and one sentence introducing namespaces is shortened. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sentences joined by semicolons now state how their clauses relate, short runs of sentences in the orientation and closing are joined, and the namespace introduction drops a sentence that only announced the next section and a second link to the same page. Code, headings, and anchors are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The opening says what cargo-cgp and the documentation do for a missing field, the diagnostic walkthrough names the help line's edit, and the wiring-cost, bundle, and check passages say what a reader has to do instead of describing the table in the abstract. The migration intro states that upgrading needs source changes and names presets and the prelude imports first, and the closing suggests trying CGP on one existing problem. The cargo-cgp qualification keeps its canonical wording. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
"Why Rust allows this only once" drops from four paragraphs to three: the guarantee coherence gives, the workaround and CGP's providers, and the context, keeping both links and leaving the rules' detail to Bypassing coherence. The section titles and the pull quote balance their line breaks, so a wrapped title no longer ends on one word, and the `T: Display` bound stays on one line on a phone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The caption under both code windows opened with "Both implementations compile", which read as though the rejected block compiled too. It now opens with "With CGP, both encoders compile". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The features lead states that the features follow from choosing providers per application, instead of attaching the claim with a trailing "which". The cost lead drops the vague "and other costs", the ecosystem row calls cargo-cgp CGP's error toolchain, and the learning row says how the agent skill helps instead of ending on a participle. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The code windows' labels, the caption, and the pull quote now say which code compiles and which provider each type selects; section 1 explains the overlap through `String`'s two traits before naming coherence; and the feature, breadth, cost, and route copy says what a reader can do. The tag line and the reassurance line stay verbatim. The caption box widens so the longer pull quote keeps one line at desktop widths, and code inside the quote sets a little smaller than its heading type. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The coherence diagram showed one concrete impl failing with E0119; it now shows the page's two overlapping blanket impls, the second rejected, with Rust items in a monospace font. The split diagram labels each provider `impl StorageObjectFetcher<Context>` as the page declares it, and its provider boxes no longer reach the image's right edge. The wiring table's "resolved at compile time" label no longer runs into the table's border. The coherence diagram's alt text follows its content. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The label "the context's wiring selects one provider" floated beside the consumer trait with only an arrow out of it. It is now a box below the consumer trait, which an arrow leads into, so the diagram traces a call through the consumer trait and the wiring to the provider. The diagram's description and the page's alt text say the same. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The arrowhead marker scales with the stroke, so at a 2-unit line it drew a 14-unit head that covered the split diagram's short drops to the two providers. All three diagrams now use a 10-unit head, and the drops to the providers are longer, so each arrow's line shows beneath its head. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The split diagram and the wiring table now set code and Rust items in monospace, as the coherence diagram does, with prose labels in sans. The split diagram's provider row gains room for its monospace labels and sits within the image's margins, the wiring table's columns and call-site box are widened for theirs, and both drop the empty band below their last box. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Twelve Concepts pages opened without saying what they cover, which the explanation guide asks of every page; each now states its route in one sentence after the opening. The comparison links in the closing lists start with a capital and use one colon, a pseudo-cleft on Bypassing coherence and on Modularity Hierarchy reads directly, Consumer and provider traits drops a first-person "us", and Checking your wiring links the site's `cargo cgp check` page and names the working `App` its supertrait check runs on. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A natural-writing pass over the 19 Concepts pages joins runs of short sentences with connectives that state their relationship, removes the remaining sentences that delay their subject, and lets each sentence pick up from the one before. No claim, snippet, or anchor changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
example-code pins cgp 0.8.0 from crates.io instead of the repository patched to a sibling checkout, so CI no longer checks out cgp beside the website. The 34 compile-fail snapshots that quote cgp's sources are re-blessed: they now name them through trybuild's $CARGO path, and their quoted lines change only in line numbers and gutter width. The README describes the pin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The cgp-skills submodule moves to the skill that describes cgp v0.8.0 and cargo-cgp v0.1.0, with its revised version check and installer list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The post's filename takes the release date, 2026-11-18, and the test that reads the post follows the rename. The cgp v0.8.0 and cargo-cgp v0.1.0 release notes carry crates.io's publish date for both. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The cgp-serde v0.3.0 and Hypershell v0.2.0 pages carry the release date, 2026-11-18, which both projects publish on. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
soareschen
marked this pull request as ready for review
November 18, 2026 10:29
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.
Overview
[claude-opus-5-5] This PR publishes CGP v0.8.0 on the site, with a redesigned front page and theme and documentation that explains Context-Generic Programming beyond the tutorials. The docs gain the Concepts, Reference, Tooling, Comparisons, Projects, Resources, and Release notes sections beside the existing tutorials and AI section. A test-only
example-codecrate compiles the pages' code againstcgp0.8.0 from crates.io in CI.Impact
Merging deploys the site, because
deploy.yamlpublishes every push tomain. The merge carries no conflict, sincemainholds no commit this branch lacks, and the announcement bar points at the v0.8.0 post, dated 2026-11-18.Areas needing attention
cgp-examples'web-app, and the cgp-serde post's two "Full Example" links, stay stale until those repositories' branches merge.deploy.yamlruns for the first time at the merge. Its build steps matchtest-deploy.yaml's, which pass on this branch.