-
Notifications
You must be signed in to change notification settings - Fork 779
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
Debug stepping behavior very poor for loops over arrays #12
Labels
Bug
Impact-Medium
(Internal MS Team use only) Describes an issue with moderate impact on existing code.
Ready
Comments
Removing the VS 2015 milestone on this guy as it would not be approved by shiproom at this point (plus no fix imminent AFAIK). |
Fixed by above PR |
liboz
pushed a commit
to liboz/visualfsharp
that referenced
this issue
Oct 17, 2016
making identity more efficient
nelak
pushed a commit
to nelak/visualfsharp
that referenced
this issue
Nov 27, 2016
Added more printing for tests for records
kant2002
pushed a commit
to kant2002/fsharp
that referenced
this issue
Mar 17, 2023
Temporary fix, remove when upstream dotnet#13786 is fixed.
nojaf
pushed a commit
to nojaf/fsharp
that referenced
this issue
Oct 25, 2023
Temporary fix, remove when upstream dotnet#13786 is fixed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
Impact-Medium
(Internal MS Team use only) Describes an issue with moderate impact on existing code.
Ready
Opened by: latkin
for loops over list seq and string all exhibit nice, consistent debug stepping behavior, but for loops over arrays don't work well at all. We should correct the debug range assignments here so that this is consistent.
![19f2qwf](https://cloud.githubusercontent.com/assets/5175830/5735853/20edcc6c-9b82-11e4-8f0b-389d42cf2687.gif)
See example here (VS 2013, "just my code" off, "managed compat mode" disabled)
Loops over ranges are also inconsistent, but at least usable, so as a lower priority item we should fix those, too.
The text was updated successfully, but these errors were encountered: