splitjoin.vim VS book

My splitjoin plugin handles your examples, in case you're open to non-LSP, non-treesitter solutions: https://github.com/andrewradev/splitjoin.vim

To avoid the practical issues with master/main, a simple solution is to mirror branches in a github action. I had to fork the action itself to fix an issue, but yeah, it works fine.

Yes, sorry, should have done that the first time I encountered the bug. I rediscovered the bug and I opened a new issue.

I quite like https://github.com/AndrewRadev/splitjoin.vim . There are defaults for some filetypes and you can add "recipes" for whatever you want.

splitjoin to alternate between abbreviated and expansive syntaxes for hashes, arrays, method calls...

To clarify a bit, "a regex approach" doesn't mean s// :). For example, I've got a few mini-parsers for specific cases like rust structs or ruby methods and hashes that handle nesting and more complex structures. Vim's built-in search functions also allow checking the syntax tree, which is how vim-ruby implements a few basic text objects, too. I feel like there's a common misconception that all of Vim is just dumb regex-matching, while regexes are just one of the tools available.

https://github.com/AndrewRadev/splitjoin.vim I noticed I often format calling a function with a lot of parameters from

For the described use case https://github.com/AndrewRadev/splitjoin.vim

I personally use this plugin: https://github.com/AndrewRadev/splitjoin.vim I usually forget I have it installed, but when I remember, it always does what in want in all the languages I use

My first port of call was to google learn rust which lead me to "the book". The book is a first steps guide written by the rust community for newbies (or Rustlings as they're called) to gain a 'solid grasp of the language'.

Before Prodzilla, I’d read 'The Book' a couple of times, and had made my way through Rustlings, but hadn’t yet built a serious project in Rust.

To answer your last question;

Start with the Rust book.

https://doc.rust-lang.org/book/

Then do Rustlings until the syntax becomes muscle memory.

Then join the Discord and start doing little projects.

You won’t get up to the proficiency of other languages as quickly in Rust. It takes longer. For me it’s taking a lot longer, but I enjoy it.

Before diving into these repositories, familiarize yourself with Rust and its development ecosystem. The official Rust book is an excellent resource for developers at all levels. Each repository has documentation on how to contribute, covering code style, issue tracking, and pull requests.

This is my third Rust book after the official book and Rust in Action. The other two books are great, but they were too theoretical for me. I'm a slow learner and had much trouble grokking Rust's features and idiosyncrasies. When I was done with these books, I was lost and unsure of what I could do.

It's the same reason everything digital and downloadable isn't free: there's a cost to create it and there's a value to it.

For a language developer to charge for a book about that language, I think that's a completely valid way to make some money off of their work.

Even the Rust book, "The Rust Programming Language" is available freely online [0], but also as a print and ebook for sale via NoStarchPress [1].

[0] https://doc.rust-lang.org/book/

[1] https://nostarch.com/rust-programming-language-2nd-edition

You know you can just read it online right now in 2 different variants It does contain some systems programming.

I am looking at The Book (https://doc.rust-lang.org/book/), but hoped there was an amazing person on youtube.

Yeah, I'll build something, finally trying webassembly.

https://doc.rust-lang.org/book/ https://github.com/rust-lang/rustlings https://doc.rust-lang.org/rust-by-example/