Skip to content

Workaround for #15972#15982

Merged
vzarytovskii merged 3 commits into
dotnet:mainfrom
vzarytovskii:workaround-for-15972
Sep 16, 2023
Merged

Workaround for #15972#15982
vzarytovskii merged 3 commits into
dotnet:mainfrom
vzarytovskii:workaround-for-15972

Conversation

@vzarytovskii

@vzarytovskii vzarytovskii commented Sep 15, 2023

Copy link
Copy Markdown
Member

After talking to @0101, we decided to make a workaround for #15972 by not excluding parsing/syntax errors from semantic ones, just in case if proper fix doesn't make it to P3.

Worst case scenario, parsing errors will be doubled.

It shows errors right now:

image_2023-09-15_15-23-26

@vzarytovskii vzarytovskii requested a review from a team as a code owner September 15, 2023 13:28
@vzarytovskii

Copy link
Copy Markdown
Member Author

Alright, some of the diagnostics tests are expectedly failing, I will either fix them or disable (since we'll likely revert the change once roslyn has a fix).

…ail once we rollback the change, but forget to rollback tests
@vzarytovskii

Copy link
Copy Markdown
Member Author

Ok, not proud of the fix, but it will fail if we rollback the workaround but forget tests.

@dotnet dotnet deleted a comment from github-actions Bot Sep 15, 2023
@vzarytovskii vzarytovskii merged commit dea6492 into dotnet:main Sep 16, 2023
T-Gro added a commit that referenced this pull request May 28, 2026
The workaround referenced in #15982
is no longer in place, so the *_HACK_PLEASE_REFER_TO_COMMENT_INSIDE
methods are now identical to their non-suffixed counterparts.
Drop the duplicate definitions and route the call sites to the existing
VerifyErrorBetweenMarkers / VerifyErrorAtMarker helpers.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants