|
|
|
|
|
by dathinab
426 days ago
|
|
yeah I mean you are basically stuck with a few options - use C/C++ focused debugers with a rust plugin or similar (okay, not not compared to idk. debugging python in PyStorm) - rely on tracing/logging and errors reported (which might sound dump as it's basically "not" debugging, but with how the rust type system plays out and enforcement of reasonable decent code style/structure etc. this is quite often good enough) - write/extend tests (again a form of "not" debugging, but where while a "must have" even if you pinned down the bug using a debugger) - sprinkle in dbg! statements (basically print line debugging) The fact that it took like 10? yearts for anyone to write more then just tweeks to C/C++ debuggers even through rust has a lot of enthusiasts is I think telling ;) Still it looks like a real nice tool to have in your toolbox. |
|