Just run your benchmarks of actual production code with optimizations it may be helpful to know what OS you’re trying to get this to work on. I’ve not been able to mangle that elevator test in a way to prevent the optimizing-out in the five minutes I tried to do so. Wow, 0 ms! Unfortunately, that’s cause the rust compiler actually spots that the result of that elevator function is completely unused so the call just gets optimized away. Rust’s debug builds are much, much slower than release builds: $ rustc elevator.rs I’m sure it is like that for every debugger.īut rust is not extremly fast. I have however in the past used gdb to debug SWI-Prolog modules, and found that after loading your module you can simply set breakpoints in rust code normally. I’m not very experienced with debugging, let alone graphical debugging. It’s been about a decade since I last touched eclipse so I’m definitely of no help there. I believe vscode is much more popular in the rust world for easy development, so you may want to look there instead. Maybe can provide some more details there. For prolog, I use a prolog-mode package of murky origin that I once copied from which is good enough for running SWI-Prolog inside emacs, evaluating buffers, recompiling files, having a REPL, etc. For rust, i have the rustic package installed which does basic incremental compilation stuff, with red squiggly underlining in emacs of code that errors during compiles. I use emacs both for rust and for prolog development. I’m probably not really the right person to ask, as my setup tends to be a bit spartan :).
0 kommentar(er)
