Search Results for "type"

Do you ever use print() or log() to debug your code? Of course you do. IceCream, or ic for short, makes print debugging a little sweeter. With arguments, ic() inspects itself and prints both its own arguments and the values of those arguments. Just give ic() a variable or expression and you're done. ic() returns its argument(s), so ic() can easily be inserted into pre-existing code. Additionally, ic()'s output can be entirely disabled, and later re-enabled, with ic.disable() and ic.enable()...

...It supports multiple languages (C++, Python, TCL among others) via the Debug Adapter Protocol (DAP) model and provides an in-editor UI for viewing scopes, variables, stack frames, output windows and more. You configure it per-project via a .vimspector.json file (or per file type) specifying the adapter, launch configuration or attach process. Once configured you can run, pause, step into/out/over, set and clear breakpoints and inspect variables directly in Vim splits or floating windows. The UI is heavy compared to typical Vim plugins (multiple panes, layouts) but it fills the gap for users who want an integrated debug workflow without leaving the editor.

...This is invaluable for post-mortem diagnosis of production daemons where reproducing a bug in a dev shell is impractical. pyringe can inject arbitrary Python into the target process, enabling on-the-spot logging, state dumps, or gentle patching to keep a system limping along while you gather evidence. It’s also useful for forensic snapshots: enumerate objects of a certain type, find reference cycles, or measure memory pressure without pre-instrumentation. While powerful, it’s designed for careful, auditable use—showing exactly what code runs and where—so teams can regain visibility when black-box processes go sideways.