3 ms·
I've run into another one of these articles on HN before and both times I was very confused. After about 10-15 minutes of reading I'm still wondering whether I'
by _gabe_ 4y ago
I've run into another one of these articles on HN before and both times I was very confused. After about 10-15 minutes of reading I'm still wondering whether I'm reading a tutorial or a discussion about strong typing (or whatever programming concept is being discussed)? Is this article meant to be a tutorial or is it some sort of commentary I'm missing? I'm fine with either one, it just helps me get in the right mindset if that makes sense :)
- IshKebab 4y agoYeah it could do with a preword like "this is a tour of various Rust type features". The title makes it sound like it gets to some kind of point, which it doesn't. But I had to spend 10 minutes skimming it to figure that out.
- sshine 4y agoI experienced the same confusion. Looking for an opinion about Rust's type system, I am presented with a tutorial on the difference between basic number types. I even think this is a great tutorial, but I wasn't looking for a tutorial. I suppose what I've learned from this is that the type of programmer represented by the protagonist doesn't know about this, and may think it's overkill for their use of numbers. I got tired of reading the tutorial before I became smarter about how to close the gap between programmers who care about types and programmers who don't.
- zanellato19 4y agoAmos does deep dives on subjects. This is one such deep dive on Rust type system, it's limitations and why they exist.