It doesn't for me, so this might be a config issue?

When switching it only put the changes on the new branch instead of staching

And?

That seems great, but I rather have a choice to also port my changes to the new branch ever time I do switch. Will use it if there's nothing else

Honestly the only reason I'm using the GUI for switching branches is that I don't want to clutter my terminal with git commands.

Despite it doesn't help me at all. I don't want a separate app. Even more if it's $60 for a wrapper around the cli. I rather learn the cli so I can use it everywhere. And finally... No Linux port.

Oh right sorry. I did check it was the good VScode on lemmy.world, but not the programming.dev one -_-'

The worse part, you enter the blog, it looks legitimate enough at a glance, go straight to the code, then find out it's bullshit.

We need ai blog blockers now...

Easier solution: Don't use google

Inb4 normies force us to change well established terminology just to appease their fragile souls

Like git's main and master

Good meme, bad reasoning. Things like that are why JavaScript is hated. While it looks the same, It should never, and in ANY case be IMPLICITLY turned into another type.

It's simple. Like git, you search the command on the internet

That's not even funny. Just life advice

Dang. I didn't knew that 🧡 was so popular. I thought it would be ♥️ but alright

Oh, then you use and_then() or something similar.

There's also the possibility to use the guard clauses patern and do let <...> = <...> else {}.

And finally, you can always split into another function.

It's not straight rules. It depends on what makes it more readable for your case.

Use a match? Unless it's for guard clauses, a match is fine enough

It's a lot less readable imo. As well than a cargo fmt later and it's gone (unless there's a nightly setting for it)

Those async blocks exist when doing async in traits.

And I never said I respected the 4 level of indentations. That's exactly the point of those rules. Keep it lowly indented but still readable

While I totally agree with that philosophy, it heavily depends on the language.

For Rust, my philosophy is more like this:

• Impl + fn body don't count, as well as async blocks if they span the whole function
• do not nest more than one if statement. You probably better using guard clauses or matches
• do not put loops into an if statement.
• do not nest loops unless clearly shown to be (X, Y) indexing
• method chaining is free
• do not nest closures, unless the nested closure doesn't have a {} block
• do not use mod unless it's test for the current module. No I don't want to Star Wars scroll your 1000 line file. Split it.

Sad Larry's origins

Uh. Didn't knew that.

I'd even add that now 99% of the distro have a gui over the package manager. Have an android or iPhone? You already have experience in installing stuff in an easier way than windows