I wish it was more clear about the memory layout of nested variable sized data structures. As far as I can work out the max capacity is decided at construction time which makes the whole thing a lot less intriguing.
I remember a couple of these from a few years ago. Long gone now of course but a fun demo of AI hallucinating the internet endlessly, generated pages from URLs that had more URLs in them to navigate to.
I've never played those mobile ad games and this scratched my curiosity. Now you're telling me they don't deliver and I'm curious again, how do they fail their delivery?
It's easy to have that view when giving away something not that many people are interested in. Once you're a platform full of media, entertainment and social connection you have to find a way to keep serving billions of users.
I don't know D so I'm probably missing some basic syntax. If pointers cannot be copied how do you have multiple objects referencing the same shared object?
It's like how talking about the "hockey stick curve" in an exponential growth line is nonsensical. It's everywhere and the curve angles you see depend entirely on what scale you view it from.
I remember learning about this gotcha around the time that Go was coming out. I was very disappointed that they were sticking to this behaviour around the same time that JavaScript was fixing it. As a new language they get less sympathy from me.
It is built into Android. Go to twitter.com, log in and then accept the install prompt that appears. It integrates seamlessly with link sharing OS UI and jump lists.