Revert the sonic decl/impl split merge from main - #84831
Merged
Merged
Conversation
…ery (dotnet#84818)" This reverts commit 24f9a0c.
…ime compilation (dotnet#84813)" This reverts commit 9f2738a.
|
Azure Pipelines: Successfully started running 2 pipeline(s). There may be pipelines that require an authorized user to comment /azp run to run. |
Member
Author
|
/pr-val |
Contributor
|
View PR Validation Run triggered by @chsienki Parameters
|
davidwengier
approved these changes
Aug 10, 2026
akhera99
approved these changes
Aug 10, 2026
JoeRobich
approved these changes
Aug 11, 2026
333fred
added a commit
to 333fred/roslyn
that referenced
this pull request
Aug 11, 2026
…-15-langver * upstream/main: Unsafe evolution: allow await in unsafe context (dotnet#84616) Fix empty localization stage on non-main/release branches in official pipeline (dotnet#84845) Reorder stages for localization and build (dotnet#84841) Revert the sonic decl/impl split merge from main (dotnet#84831) AI Workflow - switch to use personal token instead of organizational (dotnet#84832) [main] Update dependencies from dotnet/arcade (dotnet#84819) Do not offer introduce parameter for incomplete calls (dotnet#84769)
chsienki
added a commit
that referenced
this pull request
Aug 21, 2026
…#84844) Re-lands the sonic decl/impl split (backed out in #84831 to unblock insertions) together with the slow-discovery perf work (#84808) and a new fix that removes the remaining cold-allocation regression on fallback components. ## Why this is safe to re-land now The split was reverted because a VS insertion showed a cold-allocation regression on fallback-heavy scenarios (Component Classification, cohosting completion) with no offsetting speed gain. This branch addresses the root cause rather than just re-applying the revert. ## What's here 1. **Un-revert** of #84831 -- restores the sonic merge and the fixes that landed on top of it (#84818 fallback child-content discovery, #84813 RZC public-API compat, #84795 formatting options). 2. **#84808** -- slow discovery resolves fallback types via the declaration table (`GetSymbolsWithName`) instead of a per-tree semantic model, and discovers only the fallback types rather than re-walking the whole augmented compilation. (Removed the +535 MB semantic-model regression.) 3. **Reuse the initial parse for fallback discovery** (new) -- the remaining regression. ## The new fix A fallback component (an `@inherits`/`@implements`/`@typeparam` header, or body markup the analysis can't route) can't be split, so its descriptor comes from discovery over an augmented compilation. Each fallback component was being processed **twice**: the generation engine's initial parse, then a freshly created declaration engine that **re-parsed the same source** just to produce a discoverable decl. For an app where nearly every component `@inherits` a base (MudBlazor, OrchardCore) every component is a fallback, so that second parse dominates cold discovery allocation. The split phase already builds the discoverable declaration surface for a *split* component from the nodes it just classified. This builds the same surface for a *fallback* component and stashes it on the document node; the generator lowers it in place -- reusing the initial parse -- instead of re-parsing through a separate engine. It's never emitted to pre-compilation (the bodiless type shell still fills that role for C# type resolution); only its syntax tree feeds slow discovery. The rare shapes with no render method or namespace keep the re-parse path. ## Measurements Cold source-generator allocation over 100 fallback components (in-memory A/B): | | Allocated | |---|---| | Pre-split baseline | 17.1 MB | | Sonic + #84808 (before this fix) | 19.6 MB | | **This branch** | **13.6 MB** | The fallback path is now **below** the pre-split baseline -- a genuine win, not break-even. ## Validation - `Microsoft.NET.Sdk.Razor.SourceGenerators.UnitTests`: 219 passed / 1 skipped (incl. #84818's fallback child-content test). - `Microsoft.AspNetCore.Razor.Language.UnitTests` (component / tag helper / split / bind / discovery / clone): 1672 passed. - Razor compiler builds clean. Draft pending the RPS + Speedometer insertion run. ###### Microsoft Reviewers: [Open in CodeFlow](https://microsoft.github.io/open-pr/?codeflow=https://github.com/dotnet/roslyn/pull/84844) --- ## Update: warm/interactive path fix (html-span completion) A matched-baseline Speedometer re-run showed the cold-discovery regressions gone but a smaller residual on **html-span completion in a component** (`CLR_BytesAllocated_devenv`) -- the interactive/warm path, a different signature than the cold source-generator work above. Root cause: the fallback decl incremental pipeline compared decls by **instance**, while the split-decl (`DeclSources`) fast path compares by **text**. A fallback component's decl is markup-free and checksum-suppressed, so a markup-only edit (every keystroke during completion) yields a byte-identical decl -- but the instance changed each run, invalidating the parse and, through the `Collect`, re-running slow discovery over *every* fallback component on each edit. Fix: compare fallback decls by text (`Text.ContentEquals`), mirroring the fast path. A markup-only edit now leaves the fallback decl `Unchanged`, keeping its parse and slow discovery cached. Measured (100 fallback components, warm re-run on a markup edit): | | warm alloc | |---|---| | Pre-split baseline | 0.41 MB | | Before this fix | 3.2 MB (~8x) | | **After this fix** | **0.42 MB** | Guarded by `IncrementalCompilation_WhenFallbackComponentMarkupChanges_SlowDiscoveryStaysCached` (verified to fail without the comparer). Full SG suite 220 passed / 1 skipped.
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.
Backs the
features/sonicdecl/impl split out ofmainto unblock insertion. Reverts the merge (#84778) and the commits that stacked on top of it and cannot stand without it.What reverts
Merge/sonic into main-- the whole feature body (reverted with-m 1, keeping pre-sonicmain).GetCSharpDocument()/GeneratedCode-- these were re-added to shim sonic's API removal; reverting the merge restores the originals, so the shim would double-define them.CSharpFormattingOptionsHelper.cs, a file that only exists because of sonic.What is kept
The other post-merge commits are independent of sonic and stay: arcade bumps, SDL param removal, CS8802, #84758 (syntax-tree sharing), and the two Razor features that merely shared files -- #84760 (unbound-attribute warnings) and #84764 (empty-outer-tag warning).
Preserving #84760 needed one manual resolution in
UnresolvedAttributeIntermediateNode.cs: sonic added theCloneNode()/Clone()overrides and #84760 later added one property assignment insideCloneNode. The overrides are sonic infrastructure and go with the revert; #84760'sIsDirectiveAttributeCandidateproperty and all its real usages are untouched.Validation
Razor.slnfbuilds clean (compiler + all tooling projects, including the ones Always pass C# formatting options to Razor functions #84795 touched).Microsoft.NET.Sdk.Razor.SourceGenerators.UnitTests: 215 passed.Microsoft.AspNetCore.Razor.Language.UnitTests(component / tag helper / bind / unbound-attribute): 1593 passed -- confirms Add warnings for various unbound attributes in Razor #84760's kept feature still works.Note
Reverting the merge means re-landing
features/soniclater will need this revert itself reverted first -- expected for a back-out.Microsoft Reviewers: Open in CodeFlow