Viewing profile — ohr

(Author here) yes! I also wrote about this (specifically in Python->Rust FFI) in another article: https://ohadravid.github.io/posts/2023-03-rusty-python/#v2--...

(Author here) thanks! Even as an experienced Rust developer, this is a lot of syntax which is part of what makes it archaic I think. As usual with Rust most of it is due to inheren…

But if you let it run the tests, it’ll just do that on its own (or delete the tests, but usually it won’t), which is very useful and seems to match the article’s sentiment.

Used the Save Page WE Chrome extension to capture the html (after cleaning up with inspect element + delete), and added a bit of custom JavaScript to scroll everything to the right…

(Author here) I'm a huge fan of the "How to speed up the Rust compiler" series! I was hoping to capture the same feeling :)

I think that since the 1.5% one is only for aarch64 it's a bit unfair to claim the full number, more like 1/2 if you consider arm/x86 to be the majority of the (future) deployments…

Thanks! Would be interesting to see if Rust/LLVM folks can get the compiler to apply this optimization whenever possible, as Rust can be much more accurate w.r.t memory initializat…

(Author here) Thanks! That's useful feedback. I also agree - the final article isn't skim-friendly enough, which drives away some readers.

In WMI, the fields are lazy loaded when you do a `*` query, but the real crate [does use the same Serde reflection tricks]( https://github.com/ohadravid/wmi-rs/blob/main/src/query.…

> don't you have to get your version's struct data member type correct No, since Serde will happyly fill a `u64` field with any other `u{8,16,32}` value, and even with signed types…

That's understandable, but I think it depends on how many different structs like this you have and how many fields you need to work with (for our usecase, we had tens of structs wi…

(Author here) I needed to do a bit of "reflection" in a Rust crate but didn't want to implement a procedural macro, so I used Serde (which is a (de)serialization crate) instead. Th…

Thanks, I hate it! Jk, but would you consider this a good solution overall?

well yes! also calling an answer which mentions c++ as well “off-topic”, it’s not like I wrote a haiku about marmalade. And why insist on deleting if people found it useful? It’s l…

The magic for HN! Added this link to the post as well, thanks!

(author here): on the contrary, my point is that I was wrong(ish), and I often think about that before I get angry at other people on the internet. The other point is that there's …

author here: but do you find the article helpful in making you less angry? also: > I'd be angry all the time if I was coding C or C++ or C/.C++ or C-- or anything to do with C lol

Author here: actually, in this analogy (as this is just a demo library), the polygons change each time so we couldn't use this type of optimization (at least not in a straightforwa…

Author here: For the original library we did all the numpy tricks we could think of, but we really needed to do this type of exhaustive search for some of the data. If someone want…

Author here: I agree, that's a great perf advice (esp. when you can restructure your code). I couldn't get into a this in the article (would be too long), but this is a great point…