[flagged]
I'm sure they'll change things because the community really doesn't like it. I believe.
Rust, RR, Neovim: A perfect debug combination
61–70 of 102 posts
Re: Rust, RR, Neovim: A perfect debug combination
#62Anyone got other useful tools for debugging within (neo)vim? Just seamlessly putting down breakpoints, stepping through code execution, and getting a fully fledged debugging UI experience (a la Visual Studio or Remedy BG)? This is possibly the only thing I miss from developing on Windows, and it's a shame! EDIT: I specified 'within vim' but actually I'd be down for standalone Linux app recommendations too.
A couple of details have changed since that post. The only one that you might care about is that I now have two tmux panes with gdb-dashboard. This is meant to use space better. One pane has all of the variables and nothing else. The other has everything else.
If you care about that, I'll tell you how to do it.
[1]: https://gavinhoward.com/2020/12/my-development-environment-a...
Re: Rust, RR, Neovim: A perfect debug combination
#63Earlier quoted context omitted.
It's a real shame that it can't be made to work on arm systems
Readme and latest release note says it now supports Neoverse N1 (ampere altra, graviton2 and maybe some cortex ones) as well as Apple M1.
Will have to check that out!
Re: Rust, RR, Neovim: A perfect debug combination
#64Earlier quoted context omitted.
We, the R-word foundation, hereby and publically do not endorse the online gathering under this comment, as it does not: - follow local health guidelines - may attract people wearing fireguns These breaches of our big CoC are not appreciated and we will spend all of our sparse funding now to drag you to court.
I just hope Rust won't end up being forked tho. We had such an amazing community around it...
But since the name it's the only thing that is getting in the way with this new (draft) policy, you wouldn't really have to fork the language and the tooling etc. All you have to do is to just use this new made up name in place of rust (and similarly for cargo) and you've achieved independence with a fraction of the cost.
E.g.
Rust -> Crust Cargo -> Embargo
"Hey, here's a quick Crust tutorial: check out this git repo and run: embargo build"
Re: Rust, RR, Neovim: A perfect debug combination
#65Earlier quoted context omitted.
Readme and latest release note says it now supports Neoverse N1 (ampere altra, graviton2 and maybe some cortex ones) as well as Apple M1.
Wow! That's amazing, i thought there were architectural issues that prevented it (something about interrupt timings sometimes increasing the number of instructions non-deterministically iirc). Will have to check that out!
Re: Rust, RR, Neovim: A perfect debug combination
#66Earlier quoted context omitted.
I just hope Rust won't end up being forked tho. We had such an amazing community around it...
For the sake of the argument, let's imagine that you fork rust. You'd have to come up with another name for it right? But since the name it's the only thing that is getting in the way with this new (draft) policy, you wouldn't really have to fork the language and the tooling etc. All you have to do is to just use this new made up name in place of rust (and similarly for cargo) and you've achieved independence with a…
Re: Rust, RR, Neovim: A perfect debug combination
#67[flagged]
This is unproductive. I have significant criticisms of the policy draft, but this is not helpful.
> we invite you to review (..) and share any feedback (...). Your responses will help us ensure the Rust Trademark Policy is useful for all!
I'm bringing attention and visibility to the proposal and hopefully help the foundation receive valuable feedback from more people.
Re: Rust, RR, Neovim: A perfect debug combination
#68[flagged]
I started watching [3]. I have no stakes in this, but a lot of stuff I should be enraged about... I'm just not? Doesn't look fundamentally different to Debian or Firefox trademark policies. I guess it is an abrupt change in trademark enforcement for Rust.
I've got a couple small things I don't like, but once again, it seems to be right in line with other open source trademark policies. I just had never looked closely at them before
Re: Rust, RR, Neovim: A perfect debug combination
#69Investing in a good debugging tool and knowing your way around using it well, makes all the difference.
I've been using Rust on Windows, LLDB is just pain. Not being able to see content of enums is a show stopper, luckily VSCode has C++ debugger by Microsoft that works flawlessly.