I miss the usize type when I'm not coding in Rust. I find distinguishing between 'an integer representing a quantity' and 'an integer representing an array index' to be very helpful sometimes.
miniblog.
Related Posts
Uniform function call syntax treats `fido.bark()` the same as `Dog::bark(fido)`.
This seems like a really nice way of representing methods in a language. Are there any downsides? There are plenty of languages without this.
Pharo is moving away from representing instance variables and methods as strings. Instead, they're more powerful objects! https://www.slideshare.net/mobile/MarcusDenker/lecture-27685035
This enables autogenerating accessors, ORM style relationships, and easier static analysis of methods.
On representing game worlds in Rust using Entity-Component-System, modelling state, and avoiding self-borrowing: