Skip to content

Complete the Pattern matching section with deconstruction coverage and the introductory tutorial #55928

Closed

Description

@BillWagner

Everyday C# PR 21 — Pattern matching: deconstruction + tutorial

PR 21 is the committed clean boundary that fully completes Pattern matching (§11). Once the overview/basic-pattern and advanced-pattern-form work is live, this closes the remaining core article gap and moves the introductory tutorial into Fundamentals, without pulling the optional Functional techniques tutorial into September's scope.

Revise deconstruct.md to cover records, tuples, custom Deconstruct, and mixed deconstructions at Fundamentals level. Pull tutorials/patterns-objects.md into fundamentals/tutorials/pattern-matching.md, updating snippets, toc.yml, and redirects (including the former functional/deconstruct.md path). Leave the advanced data-driven pattern tutorial where it is unless implementation finds a safe, already-planned move.

Done when §11 has no remaining planned core gaps, deconstruction coverage is coherent with tuples/records/custom Deconstruct/Discards, the tutorial is adapted with redirects, and no former functional/ deconstruction path breaks. See the Phase F plan for scope.


Associated WorkItem - 632370

Activity

  1. self-assigned this
    on Sep 9, 2026
  2. added
    🗺️ mapQUESTOnly used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
    on Sep 9, 2026
  3. removed
    🗺️ mapQUESTOnly used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
    on Sep 9, 2026
  4. added
    📌 seQUESTeredIdentifies that an issue has been imported into Quest.
    and removed
    🗺️ reQUESTTriggers an issue to be imported into Quest.
    on Sep 10, 2026
  5. added
    🗺️ mapQUESTOnly used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
    on Sep 11, 2026
  6. removed
    🗺️ mapQUESTOnly used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
    on Sep 11, 2026
  7. added
    🗺️ mapQUESTOnly used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
    on Sep 29, 2026
  8. removed
    🗺️ mapQUESTOnly used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
    on Sep 29, 2026
  9. added
    🗺️ mapQUESTOnly used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
    on Oct 5, 2026
  10. removed
    🗺️ mapQUESTOnly used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
    on Oct 5, 2026
  11. added a commit that references this issue on Oct 6, 2026
    67daa56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions