looking at the github.com/sirnewton01/godbg project by chris mcgee gbd integration with golab seems feasible.
i have not often had the need for debugging but in some cases it is very much called for and then often obstructed by the the unwieldy usage of gdb.
so i want to add this as a long term goal to collect ideas and considerations.
the first substantial one is that golab needs some kind of lockdown mode. so files and document buffers cannot be changed during the debug run. because golab is a shared and collaborative workspace there needs to be initialization sequence for the lockdown other collaborators can object to.
that reveals other questions of which aspects of the ui and control are shared.
looking at the github.com/sirnewton01/godbg project by chris mcgee gbd integration with golab seems feasible.
i have not often had the need for debugging but in some cases it is very much called for and then often obstructed by the the unwieldy usage of gdb.
so i want to add this as a long term goal to collect ideas and considerations.
the first substantial one is that golab needs some kind of lockdown mode. so files and document buffers cannot be changed during the debug run. because golab is a shared and collaborative workspace there needs to be initialization sequence for the lockdown other collaborators can object to.
that reveals other questions of which aspects of the ui and control are shared.