Comments URL: https://news.ycombinator.com/item?id=49259181

Points: 5

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=48677005

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47936051

Points: 5

# Comments: 0

https://ohadravid.github.io/posts/2023-03-rusty-python/#v2--...

As usual with Rust most of it is due to inherent complexity: for example, when you deal with raw pointers, you need to specify if they are const or mut, and you must have a syntax that’s not &, and not too wordy: so * is a good choice (might be changed to &raw in the future!). And if you want to say that something is generic and the generic parameter is a pointer… you just end up with a lot of syntax.

I also agree - the final article isn't skim-friendly enough, which drives away some readers.

No, since Serde will happyly fill a `u64` field with any other `u{8,16,32}` value, and even with signed types (as long as the actual value is non-negative) - this is sort of what happens when you deserialize a JSON `[1, 2, 3]` into `[u64]`.

There's also an Alternatives section in the article about other approaches that can achieve similar results, but of course 'do nothing' is also a valid option.

Edit: > If actually concerned about the need to know UI8 ..

Just a small note: even if you don't care about the fact that it's a UI8, you still have to use the correct type. For example, if the field happens to be returned as UI4, this code won't work!

This is also a deep dive into Serde internals - hope you'll like it!

Comments URL: https://news.ycombinator.com/item?id=42379172

Points: 2

# Comments: 0

And why insist on deleting if people found it useful? It’s literally at the bottom of the page, so it’s not a public menace or anything.

The other point is that there's (usually) no need to choose between good moderation and civility, and at least IMO "blatantly off-topic and should be deleted" really fails at being civil.