If a item can have different type, those label fields are actually quite useful. So I don’t see the problem

You guys have docs?

Sadly it doesn’t fix the bad documentation problem. I often don’t care that a field is special and either give a string or number. This is fine.

What is not fine, and which should sentence you to eternal punishment, is to not clearly document it.

Don’t you love when you publish a crate, have tested it on thousands of returned objects, only for the first issue be “field is sometimes null/other type?”. You really start questioning everything about the API, and sometimes you’d rather parse it as serde::Value and call it a day.

To whoever does that, I hope that there is a special place in hell where they force you to do type safe API bindings for a JSON API, and every time you use the wrong type for a value, they cave your skull in.

Sincerely, a frustrated Rust dev

My attempt to explain was squashed by this comment

I do push often as I’m often switching between two devices. And I do make draft PR so I got an easy git diff that I can live reference with

NGL I 'm a bit like that. I often do “work” commits so that my working tree is a bit more clean/I can go from working state to working state easily.

But before a PR, I always squash it, and most times it’s just a single commit

Let’s just hope that they won’t use it as a justification to put ads in your browser, or go the brave route.

Well until you are deep into trait/future/generic territory. Because then you’ll go in big fuck (full type being in a separate file) not being correct somewhere in this shit.

Don’t get me wrong, I love rust. But those area really need some love

They created it. The compiler says the jump function is in src/main.rs

Would be cool to be AI horde compatible and just ditch the GPU requirements entirely.

I don’t think everyone got a GPU that could run stable diffusion easily, even more for laptops

It’s not that bad. It definitely helps in long functions.

I’m an advocate for code commenting itself, but sometimes it’s just better to comment on what you’re doing, and in those cases it helps to over commentate.

Instead of letting the reader interweave code reading and comment reading, I think it’s better to do either. Either you go full self describing code, letting the reader parse it as code,m, or you abstract everything, making it more of an explanation of your reasoning, and abstract lines that may look too complicated.

Not every comment needs to be useful, but I still write them to not have this switch between reasoning and thinking in code. It can also double as rubber duck debugging too!

No one diss the gaming demon summoning circle! Sacrifice him!

But at least Firefox is just compatibility, and not phasing out v2

ROG spending all the points in style again

… And it’s working

I don’t know and that’s the problem :(

I keep asking myself what to choose, only for changing it a day after cursing myself to choose a stupid name.

Big endiant is great for intellisense to quickly browse possibilities, since it groups it all in the same place. But that’s also a detriment when you know what you want. You can start typing without the prefix but you’ll have to go through the better suggestions of intellisense first.

Little endiant is the same thing, but in reverse. Great when needed, but bad for browsing.

Although I do have some fix I’m starting to use. But it’s not applicable everywhere, and not in every language.

What I do is use module as prefix. Instead of dialogue_file_open, I create a file_open in the dialogue module, allowing either directly calling file_open, or dialogue::file_open. Using intellisense on the module allow for easy browsing too!

Although in OP’s post I’d rather have file_open_dialogue as it convey the more significant meaning, being to open a file, first. Then “dialogue” is just the flavour on top

Example?

Well it ses that bing is down too, and most independent search engines are a warper arround bing so…

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…

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

Like git’s main and master