Skip to content

[v0.2] Cut Wright over to workshop-rs #143

Description

@Teakowa

Workshop dependency: workshop-rs#2
Release coordination: #135

Goal

Make workshop-rs the single canonical Workshop implementation consumed by Wright and remove duplicate Workshop semantic ownership from this repository.

Scope

  • Replace Wright-owned canonical Workshop parser/catalog/emitter/WIR implementation dependencies with the exported workshop-rs surface.
  • Move or adapt WIR ownership so canonical Workshop semantic types no longer live in a source-language/Wright-owned mixed IR boundary.
  • Update analyzer, driver, conversion, diagnostics, language-service, tests, fixtures, and distribution code to consume workshop-rs where Workshop semantics are required.
  • Preserve existing Wright user-visible compile/check/lint/analyze/inspect/convert behavior during cutover.
  • Remove duplicate canonical Workshop catalog/parser/emitter/validation code once callers are migrated.
  • A temporary compatibility crate/module may only re-export or adapt workshop-rs; it must not remain a second semantic implementation.
  • Pin/document the consumed workshop-rs version/commit during the pre-release migration.

Non-goals

  • Moving Wright lint, agent, LSP, or orchestration responsibilities into workshop-rs.
  • Full OPY/DEL provider extraction.
  • Expanding Workshop syntax/catalog beyond what workshop-rs declares as part of this cutover.
  • Maintaining two canonical Workshop implementations for compatibility convenience.

Acceptance criteria

  • Wright's production dependency graph consumes workshop-rs for canonical Workshop semantics.
  • No second canonical Workshop parser/catalog/emitter/WIR implementation remains active in Wright.
  • Existing declared Wright workflows remain regression-green against the cutover.
  • Compatibility shims, if any, contain no independent semantic implementation and have an explicit removal path.
  • Dependency direction remains wright -> workshop-rs; workshop-rs does not depend on Wright tooling crates.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions