Please curse me with knowledge. I’m ready
Please curse me with knowledge. I’m ready
What about chess battle advanced?
tea_bag.unwrap()
I get 100m up front, right?
Right?
Delete container, rebuild container. Sometimes it’s just useful to clean up all the mess of cache files
It’s either ghosts or firmware updates. You need to be careful, as bothering the later may brick your cat into blep mode.
You’re lost. This ain’t the place to post that.
Also “candy box” is a waffle menu
Shit did hit the fan then
Ah yes. Classic summer past times.
Throwing rocks and finding vulnerability in gclib
I got nothing against other types. Just numbers/misleading types.
Although, enum variants shall have a label field for identification if they aren’t automatically inferable.
This is understandable in that use case. But it’s not everyday that you deal with values in the range of overflows. So I mostly assumed this is fine in that use case.
This isn’t even an issue of middle ware sometimes. It’s just… Knowing the DB. And I rather not spend time learning when you can just make docs
As if I had a choice. Most of the time I’m only on the receiving end, not the sending end. I can’t just magically use something else when that something else doesn’t exist.
Heck, even when I’m on the sending end, I’d use JSON. Just not bullshit ones. It’s not complicated to only have static types, or having discriminant fields
The schema is this SQL statement
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
Was an interesting read. Thanks.