Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FUSE] Add some missing runtime source mappings #9883

Merged
merged 4 commits into from
Feb 8, 2024

Conversation

chsienki
Copy link
Contributor

@chsienki chsienki commented Jan 30, 2024

Add various line mappings that are missing in runtime documents.
Commits are split between changes and baseline updates; suggest reviewing separately.

Still have more mappings to be added, but they are more involved so submitting this in parts.

Fixes #9828

Before:
image
image

After:
image
image

@chsienki chsienki added area-compiler Umbrella for all compiler issues New Feature: Fuse labels Jan 30, 2024
@chsienki chsienki requested a review from a team as a code owner January 30, 2024 21:42
@chsienki
Copy link
Contributor Author

@dotnet/razor-compiler for reviews please. //cc @ryzngard

@chsienki chsienki linked an issue Jan 30, 2024 that may be closed by this pull request
Comment on lines 2 to 5
|using System.Threading.Tasks
|
Generated Location: (317:11,0 [30] )
|using System.Threading.Tasks;|
Copy link
Member

@jjonescz jjonescz Jan 31, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The source location has a newline as the last character while the generated location has a semicolon there instead. Perhaps the mapping should be one character shorter?

I wonder if we should assert that source and generated location texts match so we don't have to check this manually.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The generated location also includes a semi-colon. I think this would be a problem, yes.

I wonder if we should assert that source and generated location texts match

I thought there was such a validation, maybe its just not called in all cases. Pretty sure I've hit it once or twice.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh huh, good catch. I'll add the assertion if we don't have it, too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, it turns out fixing the using discrepancy is significantly more involved, as it's actually a difference in parsing that's occurring.

I've backed out the using mappings from this PR, rather than try and fix a huge amount of stuff in one go.

@chsienki chsienki requested a review from a team as a code owner February 5, 2024 23:05
@chsienki chsienki merged commit 67024cb into dotnet:features/fuse Feb 8, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-compiler Umbrella for all compiler issues New Feature: Fuse
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FUSE] Missing error on nonexistent method
4 participants