Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upDebug.crash renders the debugger useless #953
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
process-bot
Mar 28, 2018
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!
Here is what to expect next, and if anyone wants to comment, keep these things in mind.
process-bot
commented
Mar 28, 2018
|
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it! Here is what to expect next, and if anyone wants to comment, keep these things in mind. |
evancz
added
the
request
label
May 22, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evancz
May 22, 2018
Member
Thank you for the experience report. I do not think this can be done without very significant changes, but I will file the note for future changes that may make it possible.
|
Thank you for the experience report. I do not think this can be done without very significant changes, but I will file the note for future changes that may make it possible. |
evancz
closed this
May 22, 2018
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
muelli
May 22, 2018
Where will that note be?
I hope somewhere where someone with the interest, time, and skill-set can find that open task and work on it.
muelli
commented
May 22, 2018
|
Where will that note be? I hope somewhere where someone with the interest, time, and skill-set can find that open task and work on it. |
muelli commentedMar 28, 2018
I wish a Debug.crash would still allow me to explore the app's state in order to understand what went wrong. Currently, however, the debugger is not responsive once Elm has crashed.