[#271] runHDBServer parametrized on DebugRunner#274
Conversation
cb45ff9 to
12fb0d5
Compare
4c2abe1 to
7826d8d
Compare
506c7e3 to
cea40af
Compare
|
@alt-romes about the Sdist tests, should I handle the source-package-repository dependence on |
Hmm. We need to make sure dap is released when we do a release, which is why this is a good CI check. A few ideas:
The benefit of not releasing immediately is bundling more changes into a single release, but then again it's not that much of a worry to release a lot. Especially since we don't necessarily envision changing @dmjio is releasing often fine for you? Thanks! |
|
I've opened haskell-debugger/dap#33 tracking the new dap release |
|
(Please add a descriptive commit message. It will help when looking at the log.) (It should mention Reviewing now. |
1be7510 to
b80f767
Compare
|
@Saizan I've done the 0.6 |
- moved DAP-related code from executable `hdb` to public sublibrary `haskell-debugger:dap` so that runHDBServer can be imported in other packages. - refactored runDebugger to take a "DebugRunner" function whose responsibility is to provide a Ghc session and a way to load the debugee home units. - The in-memory:haskell-debugger-view unit is no longer compiled via `load` to avoid unloading the modules loaded by the DebugRunner. We rely on `compileOne` instead.
|
@alt-romes done, good to merge? |
|
Ye, land it! |
runDebuggernow takes aDebugRunnerparameter which takes care of providing a session and an action to load the debuggee home units.The
DebugRunnerparametrization is pushed up the call stack until we can define arunHDBServerfunction which could be used from elsewhere to start a DAP server.