My ideal Rust workflow
This seems to be about &quot;deploy-flow&quot; or something, rather than the actual workflow, which currently is kind of horrible in Rust thanks to slow compile times and no availability of a REPL.<p>I&#x27;ve mostly written lisp in my career, with some dips into PHP, JavaScript and other various languages when needed, but mostly interactive lisp environments so far (and lately, mostly Clojure).<p>How do people develop in Rust? I&#x27;m trying to learn it, but it&#x27;s hard to jump into code-bases and understand the code as I cannot run snippets. Lots of copy and pasting into new &quot;main&quot; files is being done in order to run small snippets of code, to see what they do.<p>Another way is to isolate parts into smaller test cases, but now I have two pieces of code in two places, one in the actual program and one in the test case. And still I cannot just select code to evaluate when I need to dig deeper into the statements.<p>Difficulty to evaluate snippets of code together with the slow compile times makes it really hard (for someone used to lisps) to learn and understand Rust.<p>How does your workflow (when writing&#x2F;reading code) actually look day-to-day? If you&#x27;re writing a web server, are you really stopping the server, compiling again, run the full server when doing changes the logic for the server? That seems absolutely bananas and I&#x27;m sure I&#x27;m missing something vital for my own environment.