-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
Capture StartEndRange information in SynExpr.AnonRecd to fix #2566 #2591
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A good start here! Please dot some more i's and cross some t's and we can merge this in.
- pass openingBrace, closingBrace to genMultilineAnonRecord, too - call genTriviaFor for openingBrace, too - expand tests to cover opening braces
Adding
In record instances:
The later could be solved be using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Many thanks
You could force the comment to be printed after We can merge this PR as is, for my part. It's up to you. |
Ah thanks, that was way easier than I thought. |
|
||
let a = | ||
{| // test1 | ||
foo with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know it is the same as we have it for regular records.
But in the future, we might want to have something like
{| // foo
bar with
A = 1
B = 2 |}
I don't feel strongly about this, so no need to address this in this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should better be handled in a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good to me!
I have no idea why the CI is failing, the NuGet lock file should not be throwing errors.
I think we need to apply the steps explained here.
I'll do that in a separate PR so you can rebase with main.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is also dotnet/fsharp#13678.
I hope it is ok.
fixes the lost comments in #2566