What the heck is this paywalled article doing here? That's some reddit-level shit.
Anders429
I was originally introduced to the idea by this RustConf 2018 keynote: https://kyren.github.io/2018/09/14/rustconf-talk.html. It's rather dense though.
I did find this random article that outlines just the concept of generational indices pretty concisely: https://lucassardois.medium.com/generational-indices-guide-8e3c5f7fd594
If you want to go one step further, a lot of game development uses a generational index, where the index is both a value and a generation, allowing you to know whether the index you currently have stored references an object that has already been destroyed and replaced by another object. Basically every ECS framework I've ever seen uses this pattern.
Don't worry, I misread it the exact same way
That quote of the week is hilarious
Anyone know the motivation behind this change? I feel like it's weird, I kinda liked having the logo.
I sincerely doubt Rust would ever add something like this.
And yet, it still happens all the time.
I'm confused. What makes you think they have been put in a position of authority? Anyone can simply create a fork, or a separate project completely, and go a different direction. You're not obligated to use any third party crate.
I do agree that they handled that interaction pretty poorly, though.
Also I believe California has laws protecting your data privacy.
Bold of you to assume they even clicked the link
Same quote of the week as last week?