>you still make your changes in your favorite editor and code is still tracked in version control. Version control does not track which sequence of code snippe

>you still make your changes in your favorite editor and code is still tracked in version control. Version control does not track which sequence of code snippets you have (re)-evaluated to get to your current repl state. I'm fully aware of how editor integration with a Lisp repl works in Emacs and (to a lesser extent) Vim. >have dabbled...In the end, I'm not gonna try to convince you to try something...seem not to have super much experience with a powerful repl...etc. As with most Lisp advocates, you seem unable to a accept that I have tried it and didn't like it. Please stop throwing shade. > This assumes a lot of things around the code that you're executing. First, you've already setup a test and it's already isolated enough A test in Go is just a function, so no set up is required. A test is more isolated than an expression evaluated in a repl. It seems to me that you don't have much experience of writing tests in a modern development environment, and this is why manually recompiling parts of your codebase using Vim hotkeys strikes you as a good idea :)