No, the original program writes through iq, which is well defined. Only the optimized program writes through p+1.
Oh come on, don't make me spell it out for you. Revenge porn preys on women, child porn preys on children. Having these videos up, and allowing people to upload them, actively hurts people. Nobody is getting hurt if…
Absolutely this. The benefits of "casual exhibitionists" absolutely do not outweigh the risks and costs of having unverified and possibly illegal porn on your site.
Legally I'm not sure. But ethically, stolen TV show clips are way more justifiable than stolen porn.
An example like that is exactly why, in its current form, it's a bad idea. It's too high level. On the surface it seems like it makes code more consise and elegant, but in reality it just pushes the "ugly"…
Agreed. In Go, defers accumulate and are all called at the end of a function, which I believe is a mistake (but there are practical uses for it). I think it would be much more fitting for C just to have the defer happen…
The redesign was a massive success. The goal was to turn reddit into a typical social media property, and it worked. Real conversation was pushed aside into niche subreddits, and was replaced by typical social media…
In its current form, this is really stupid, because of something like this: guard { for (int i = 0; i < n; i++) { defer foo(i); } } Now the compiler has to: 1. implement some side of capture/closure mechanism to keep…
No, the original program writes through iq, which is well defined. Only the optimized program writes through p+1.
Oh come on, don't make me spell it out for you. Revenge porn preys on women, child porn preys on children. Having these videos up, and allowing people to upload them, actively hurts people. Nobody is getting hurt if…
Absolutely this. The benefits of "casual exhibitionists" absolutely do not outweigh the risks and costs of having unverified and possibly illegal porn on your site.
Legally I'm not sure. But ethically, stolen TV show clips are way more justifiable than stolen porn.
An example like that is exactly why, in its current form, it's a bad idea. It's too high level. On the surface it seems like it makes code more consise and elegant, but in reality it just pushes the "ugly"…
Agreed. In Go, defers accumulate and are all called at the end of a function, which I believe is a mistake (but there are practical uses for it). I think it would be much more fitting for C just to have the defer happen…
The redesign was a massive success. The goal was to turn reddit into a typical social media property, and it worked. Real conversation was pushed aside into niche subreddits, and was replaced by typical social media…
In its current form, this is really stupid, because of something like this: guard { for (int i = 0; i < n; i++) { defer foo(i); } } Now the compiler has to: 1. implement some side of capture/closure mechanism to keep…