Repository navigation
Add regression test: #6036, FCS namespace-module collision diagnostic - #20706
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
🤖 This is an automated response from Regression PR Shepherd. This regression test proves the bug in #6036 still exists when FCS uses the transparent compiler. This PR should be closed until the underlying bug is fixed. The bug: A project that defines The test: The failure: The Warning Firewall blocked 2 domainsThe following domains were blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "dev.azure.com"
- "southcentralus0.in.applicationinsights.azure.com"See Network Configuration for more information.
|
Capture diagnostics while finalizing project checks and serializing assembly signatures, then include them in project results. Namespace/module collisions are emitted when lazy signature fragments are forced, after per-file finishers return. Add the release note for the FS0247 regression fix. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Fixes #6036
FCS project checking now returns FS0247 for the namespace/module collision that was previously missing from IntelliSense diagnostics. The regression test exercises the exact two-file repro through
ParseAndCheckProject.Test:
.dotnet/dotnet test tests/FSharp.Compiler.Service.Tests/FSharp.Compiler.Service.Tests.fsproj -c Release --no-build --nologo -- --filter-method "*Issue 6036*"🤖 This pull request was created by Repo Assist, an automated AI assistant.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
southcentralus0.in.applicationinsights.azure.comSee Network Configuration for more information.
Add this agentic workflows to your repo
To install this agentic workflow, run