ML Classification 0.020141480027042014 (Old classification 0.43)
Think about the problem, come up with a solution and if you have trouble getting parts of it to work, ask those specific questions on StackOverflow. There's no simple Python function or standard algorithm here, although seasoned Python programmers might come up with very similar solutions. — Grismar28 secs ago
ML Classification 0.00436094913330326 (Old classification 0.4)
There are sites where you can get programmers to do the job. Stackoverflow will not do work for you. It will help solve specific programming issues. — Tarik47 secs ago
ML Classification 0.0031579563707528164 (Old classification 0.43)
Welcome to Stack Overflow. Do you expect the name _init_ to have special meaning? Please look at it carefully, and compare it to what is in the documentation. Hint: there's a good reason that programmers use monospaced fonts. — Karl Knechteljust now
ML Classification 0.047459025677267334 (Old classification 0.4)
ML Classification 0.05470901671562885 (Old classification 0.4)
Are you coming from Java or similar background? Things like *(new...) are typical for Java programmers making their first steps in C++. Java experience does not transfer to C++ well. I recommend getting a good C++ textbook and working through exercises. — n. 1.8e9-where's-my-share m.23 secs ago
ML Classification 0.0013838763706214964 (Old classification 0.46)
For whomever is voting to close this as general computing, please read the help center carefully: "software tools commonly used by programmers" are on-topic. Questions about using software are only off-topic if they do not "directly involve tools used primarily for programming." — Ryan M54 secs ago
ML Classification 0.004471300579812475 (Old classification 0.4)
Even in language where you can monkey patch builtins, it's usually frowned upon to actually do so, because it simply creates all sorts of issues down the line when you have to interact with 3rd parties (libraries, other programmers, etc). — deceze ♦11 secs ago
ML Classification 0.015079174071117925 (Old classification 0.4)
@justANewbie And this right here is why C++ programmers hate Code::Blocks: it does weird stuff behind your back that it isn’t supposed to do. — Konrad Rudolph7 secs ago
ML Classification 0.9866504243022405 (Old classification 1.0)
This question is more suited for Software Engineering than SO. This community is for coding related question rather than design and platform — shoaib3046 secs ago
ML Classification 0.004960248977078427 (Old classification 0.4)
@Lundin The point is to learn how to exploit a common mistake made by programmers, not to determine if programmer made the mistake or what mistake they made. Why do basketball players shoot hoops in practice without a defender? — spicy.dlljust now
2021-10-15T14:42:57.834875Z Quota has been reset. Was 8264 is now 9999
ML Classification 0.8751240079142828 (Old classification 2.25)
Design questions where there are multiple good answers possible are generally a better fit for Software Engineering rather than Stack Overflow. Stack Overflow is better suited for questions about specific, narrow problems. — Charles Duffy28 secs ago
ML Classification 0.025651315873824396 (Old classification 0.4)
Hm - a simple question and nobody knows the answer? what kind of programmers are you. You can delete everything, because I'm a lot of an asshole — Tomasz Vizaint35 secs ago
ML Classification 9.697629621934919E-4 (Old classification 0.4)
@pythonHua: volatile, like C++ std::atomic<>, forces the JVM to load or store to memory, not keep something in a register. (Registers are thread-private; cache is coherent). For more about the fact that CPUs have coherent caches, see When to use volatile with multi threading? (but note that's about C++ volatile, which forces load/store but does not give ordering wrt. other code.) Or for a Java version of that: Myths Programmers Believe about CPU Caches — Peter Cordes11 secs ago
ML Classification 0.0025943557007393186 (Old classification 0.4)
Your answer is also promoting another misconception. CPU cache is coherent. Myths Programmers Believe about CPU Caches. The thing you need to prevent is having the JIT compiler keep a value in registers. As long as volatile or synchronized forces it to actually run a store instruction, the value will become visible to other threads just by committing it to the local L1d cache, because it's coherent. (And a memory barrier will block later loads/stores until that happens). — Peter Cordes10 secs ago
ML Classification 0.014098606577668203 (Old classification 0.4)
@hookenz, not necessarily. This is a question about a tool commonly used by programmers (and not many non-programmers) and is therefore on-topic as defined in the help center. — Chris59 secs ago
Duga's Neighborhood
Duga's Neighborhood