-
Notifications
You must be signed in to change notification settings - Fork 783
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
Enabling debug breaks on |> operators #52
Comments
I continue to work on this - and my goal is to apply the change to all the pipes in both directions assuming that makes sense in the final change. |
Was this forgotten? Dropped? It would be great to see this implemented! |
Would extending this to all operators make sense? Long operator chains are used quite frequently. |
For example it's quite common to do this in web programming with the combinator models of Suave and Giraffe. Enabling better debugging/stepping of those operators would be much appreciated. |
Don Syme has guidance for people interested in offering a patch.
…On Wed, Jun 2, 2021 at 9:11 AM Chet Husk ***@***.***> wrote:
For example it's quite common to do this in web programming with the
combinator models of Suave and Giraffe. Enabling better debugging/stepping
of those operators would be much appreciated.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#52 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABFDE257FSHL4GOG3M2WMDTQZJ25ANCNFSM4A2PKWDA>
.
|
@cmeeren I'm no longer involved in the project. |
@KevinRansom Was this completed? |
Opened by antofik at codeplex
Currently, I rarely use the |> operator because of their opaqueness in the debugger, and instead have to resort to series of var names that end with more and more prime symbols. The latter is error-prone, and I'd like to be able to use |>s more confidently in my code.
This issue suggests that |> be made to generate a sequence point, at least in debug builds, so that break points can be placed on them. Additionally, the intermediate results of |> chains would have to be represented as a specially-named variable in VS's Locals variable viewer window.
Here's the CC'd conversation as Don and I discussed it on Twitter - https://twitter.com/bryanedds/status/460140352213504000
The text was updated successfully, but these errors were encountered: