error-message-index
debug-adapter-protocol
Our great sponsors
error-message-index | debug-adapter-protocol | |
---|---|---|
5 | 14 | |
93 | 1,315 | |
- | 3.0% | |
8.2 | 7.2 | |
about 1 month ago | 6 days ago | |
Haskell | HTML | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
error-message-index
-
There is No “Tooling Issue” in Haskell
Significant effort is going into resolving this issue right now and things should be much improved in 9.6. We already have https://errors.haskell.org/ which catalogues many errors with descriptions and examples. The asspciated error codes will be added to all errors once 9.6 is release for easy reference.
-
[ANN] GHCup-0.1.19.0 released
We're also delighted to announce integration with errors.haskell.org, which already has a couple of GHCup codes documented, e.g. https://errors.haskell.org/messages/GHCup-00010/
-
[ANN] First release candidate for stack-2.9.3
To support the Haskell Foundation’s Haskell Error Index initiative, all Stack error messages generated by Stack itself begin with an unique code in the form [S-nnnn], where nnnn is a four-digit number.
-
What prevents Haskell from having good error messages?
I don't think the resolved issues are actually ones about error messages. They largely seem to be meta issues about the project. As far as I know nothing that project has done has made it into a released GHC yet, but GHC 9.6 will have unique error codes for each error pointing to an entry on https://errors.haskell.org/. Both the codes and the website are achievements of that project, specifically under its error-messages-index incarnation. If you'd like to contribute you may like to read https://github.com/haskellfoundation/error-message-index/blob/main/CONTRIBUTING.md or post a message introducing yourself on https://github.com/haskell/error-messages/issues/new.
debug-adapter-protocol
-
The IDEs we had 30 years ago and we lost
> There's a strange dance of IDEs coming and going, with their idiosyncracies and partial plugins.
The Language Server Protocol [1] is the best thing to happen to text editors. Any editor that speaks it gets IDE features. Now if only they'd adopt the Debug Adapter Protocol [2]...
-
Bitty Engine: A tiny powerful game engine
Wonder if they've got support for Debug Adapter Protocol? https://microsoft.github.io/debug-adapter-protocol/
- Hi vimmers! Does any one use F[1..12] keys and what for? Cheers!
-
What a good debugger can do
> Debuggers need to do more things
It's true that coming up with an interface for an abstract debugger is harder, but it's not impossible. Microsoft create Debug Adapter Protocol (https://microsoft.github.io/debug-adapter-protocol/), which is conceptually similar for LSP. It's not perfect, but covers most basic operations pretty well, while leaving to the debugger to deal with the implementation details.
-
There is No “Tooling Issue” in Haskell
Most languages also include support for the Debug Adapter Protocol, and Haskell is no exception, so if you are so inclined, you can hook up your favorite editor/IDE and go to town.
-
Debug this meme
They're working on the Debug Adapter Protocol but it doesn't have critical mass/adoption yet. And yeah, I end up having a fair share of dbg!(foo). It's not so bad since dbg!() also returns its value, so you don't have to mess with your code too much.
-
Step Debugger Development: Debug Adapter Protocol Support
TL;DR: What would it take to implement a Debug Adapter Protocol (DAP)-based step debugger?
- DAP – Debug Adapter Protocol
-
Try TeXmacs in your Browser via WebAssembly (Mogan Fork of TeXmacs)
RDP is the Windows Remote Desktop Protocol that was in use for decades before VSCode; VSCode's own remoting doesn't use it.
I'd say that, in addition to LSP, the other big thing that came out of VSCode is DAP: https://microsoft.github.io/debug-adapter-protocol.
-
I got fired yesterday for using vim
The most important part is the JDT Languag Server, it will give you the Java tooling for writing code. I think it has DAP support as well, so with a DAP client like nvim-dap you should be able to debug as well.
What are some alternatives?
pantry
cortex-debug - Visual Studio Code extension for enhancing debug capabilities for Cortex-M Microcontrollers
haskell-mode - Emacs mode for Haskell
ghci-dap - ghci having DAP interface.
flow-storm-debugger - A debugger for Clojure and ClojureScript with some unique features.
error-messages
watchpoints - watchpoints is an easy-to-use, intuitive variable/object monitor tool for python that behaves similar to watchpoints in gdb.
text - Haskell library for space- and time-efficient operations over Unicode text.
mogan - Mogan (based on GNU TeXmacs): Let us enjoy exploring science and technology!
ghcup-hs - THIS REPO IS A MIRROR, BUG REPORTS GO HERE:
delve - Delve is a debugger for the Go programming language.