Skip to content

Conversation

@KevinRansom
Copy link
Contributor

This image shows both scenarios operating correctly

Fixes:

#15258
#14779
#14779 was caused by: the parser needing an End of block following the indented submission. We use ';;'. The end of block allows the parser to reset indent expectations.

#15258 was caused by a lack of space between the # line-number statement in the submission vsfsi prepares for submission to fsi.

Image:
image

@KevinRansom KevinRansom requested a review from a team as a code owner June 13, 2023 22:21
@inosik
Copy link

inosik commented Oct 11, 2023

Is this supposed to be released in VS 17.7? I'm still getting the issue I reported in #15258 with 17.7.5.

@vzarytovskii
Copy link
Member

vzarytovskii commented Oct 11, 2023

Is this supposed to be released in VS 17.7? I'm still getting the issue I reported in #15258 with 17.7.5.

Likely it didn't hit the bar, please check 17.8 preview and see if it works there. I am not sure we got approval for 17.7 for it

Also, it might depend which SDK is used (in global.json) and which FSI (normal or coreclr) is used.

cc @KevinRansom

@vzarytovskii
Copy link
Member

This is what I see in 17.8:

image

@inosik
Copy link

inosik commented Oct 11, 2023

Thank you for the quick answer. I‘ll wait for 17.8 then. I just wondered, because the patch is in the release/dev17.7 branch and I thought this is the branch that 17.7.x is built off.

I‘ll also check if the CoreCLR version changes anything, because I usually use the .NET Framework version.

@KevinRansom KevinRansom deleted the fix14779 branch March 21, 2024 22:25
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.

5 participants