Skip to content

test harness: ProjectCompilationHelper feeds only Sharpy.Stdlib.dll into module discovery — the CLI also feeds Sharpy.Core.dll — so in-process project tests take a different import route than sharpyc #2140

Description

@antonsynd

Found by /verify-implementation plan-0ca7b7 (fix-override lane, 2026-09-27); pre-existing at BASE acd1d40 unless noted.

ProjectCompilationHelper.WithStdlibModules adds only Sharpy.Stdlib.dll to discovery. The CLI's GetDefaultReferences adds Sharpy.Core.dll as well. So in-process project tests resolve Core's attribute-declared modules (e.g. sharpy.generators, which also spells the .NET namespace Sharpy.Generators) on the namespace route, while sharpyc project uses the attribute-declared-module route.

Consequence: the 1a3ba8d regression (SourceGenerator subclass without @OverRide → SPY0248) left SourceGeneratorTests green, and only the spec-block sweep caught it. Repro: ClrBaseOverrideRouteMatrixTests Project_NamespaceRoute vs Project cells (ba2bb63c4). Class contract: the test harness builds with the CLI's reference set, one reference authority.

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

    class-trackerThe one issue per class: carries the contract and the cell tablelane:toolingDocs, formatter, LSP, build tools, tests, CIreach:probeNeeds an escaped spelling, a wrong-annotation probe or a python3 message diff

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions