There's a reason why data races aren't considered a memory safety issue, because we have a concept that deals with concurrency issues - thread safety.
Also for all it's faults, thread and memory safety in java aren't issues. In fact java's concurrent data structures are unmatched in any other programming language. You can use the regular data structures in java and run into issues with concurrency but you can also use unsafe in rust so it's a bit of a moot point.
Arguably modern c++ ( aka if you don't use raw pointers), fits all categories.
Didn't even open the link probably
That's a fair point, I guess I used binary numbers so much i uni that I just know the small ones by heart and that's why I find it easier. Following the example, I never convert 101 as 4+0+1, I just see it and know it's 5.
Read, write, and execute are represented by the numbers 4, 2, and 1, respectively, and you add them together to get the permission
Maybe I'm the weird one here but this seems like a counter intuitive way to remeber/explain it. Each octal digit in the three digit number is actually just 3 binary digits ( 3 bit flags) in order of rwx. For example read and execute would be 101 -> 5.
At the (SQL) database level, if you are using null in any sane way, it means "this value exists but is unknown".
Null at the SQL means that the value isn't there, idk where you're getting that from. SQL doesn't have anything like JS's undefined, there's no other way to represent a missing value in sql other than null (you could technically decide on certain values for certain types, like an empty string, but that's not something SQL defines).
They're probably being downvoted for making a huge leap just from wearing pointy highheels lol. They turned a trivial reason into a non-trivial characterization/flaw about a person.
I'm on ddg and get no such issues with the same query:
I mean if you had bothered to open the article, it's in the 2nd paragraph:
The most comprehensive study of global climate inequality ever undertaken shows that this elite group, made up of 77 million people including billionaires, millionaires and those paid more than US$140,000 (£112,500) a year
Guilty Crown, as an anime it's nothing special, the openings by supercell and egoist are amazing. Not to mention the OST, which was composed by Hiroyuki Sawano, was absolutely amazing.
Linking to the great firewall article is completely nonsensical in this context, and you would be aware of that if you had bothered to open the link in my previous comment.
just so we on the same page, I'm talking about data is gathered, not whether it's protected ( legally ) , idc
Which is exactly what I'm talking about, which you would again know if you read what I linked.
I'm not a lawyer but I think somewhere in the DSL it mentions data is collected from companies within China and outside
It doesn't, what I linked to discusses the very laws you are talking about at length if you are actually interested rather than just spouting nonsense like "it's in the constitution".
Just so we're on the same page you have no idea about Chinese laws on gathering, processing and handling of data, but you heard it somewhere, repeat it, won't bother to research further and then claim there's no propaganda.
but why is it hard for you to swallow, knowing that US based companies ( with all the power they have, lawyers.. Etc ) comply with data collection laws
Because they don't. Evidenced by all the fines the EU is handing out to google, meta, etc. You could also look to all the stuff Snowden blew the whostle on. Do you think they just stopped doing mass surveillance on a global level?
Because you would be using std::shared_ptr<> rather than a raw pointer, which will automatically deallocate the memory when a shared point leaves the scope in the last place that it's used in. Along with std::atmoic<shared_ptr> implements static functions that can let you acquire locks and behave like having a mutex.
Now this isn't enforced at the compiler level, mostly due to backwards compatibility reasons, but if you're writing modern c++ properly you wouldn't run into memory safety issues. If you consider that stretching the definition then I guess I am.
Granted rust does a much better job of enforcing these things as it's unburdened by decades of history and backwards compatibility.