Speeding up the Rust edit-build-run cycle (davidlattimore.github.io)

submitted 4 months ago by copacetic@discuss.tchncs.de to c/rust@programming.dev

12 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] onlinepersona@programming.dev 1 points 4 months ago* (last edited 4 months ago)

If you’re like many developers and you generally use println for debugging and rarely or never use an actual debugger, then this is wasted time.

I weep for the time lost on debugging with println. Good grief. It's like having access to a time stopping ability and going "nah, I like trying to add a marker and tracing footsteps".

Yes, for multi threaded workloads there aren't many options, but most are single threaded and eschewing a debugger is bonkers to me.

Anti Commercial-AI license

[-] Aras@feddit.org 1 points 4 months ago

I have to admit I still readily reach for dbg! to narrow down where the problem is happening (instead of endlessly stepping through), especially in async. But when I do I put in one or two a function and upto one an await. Then I make a breakpoint before that and debug if I didn't find it by just a short look.

load more comments (2 replies)

this post was submitted on 14 Nov 2024

27 points (96.6% liked)