Re:My ideal Rust workflow
by tialaramex on Wednesday October 27, 2021 @07:53AM
(#29011972)
> If you'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?
Yes. This is definitely how I'd change the server. I wrote a server that reflected our RDF storage engine as an HTTP SPARQL endpoint. I did that in C, today I would probably use Rust. I'd expect to maybe restart the server say a dozen times in a day's work, maybe less, occasionally more.
Stronger type checking and other pre-compilation inspection might help you? You can have tooling that will show you that what you've written is nonsense and won't compile in a typical IDE like VSCode or even vim.
I don't like REPLs for this type of work, whereas they're definitely what I want for say, live coding music performance or ad hoc database queries.
Yes. This is definitely how I'd change the server. I wrote a server that reflected our RDF storage engine as an HTTP SPARQL endpoint. I did that in C, today I would probably use Rust. I'd expect to maybe restart the server say a dozen times in a day's work, maybe less, occasionally more.
Stronger type checking and other pre-compilation inspection might help you? You can have tooling that will show you that what you've written is nonsense and won't compile in a typical IDE like VSCode or even vim.
I don't like REPLs for this type of work, whereas they're definitely what I want for say, live coding music performance or ad hoc database queries.