Do you have to ban atomics to get good tool support for race detectors?
It seems that Helgrind treats atomics the same way as normal read/write operations. So, using atomics will result in lots of false positives.
Do you have to ban atomics to get good tool support for race detectors?
It seems that Helgrind treats atomics the same way as normal read/write operations. So, using atomics will result in lots of false positives.
Do you have to ban atomics to get good tool support for race detectors?
It seems that Helgrind treats atomics the same way as normal read/write operations. So, using atomics will result in lots of false positives.
Programming language dev tools – forcing conventions/breaking non-conforming code
I would like to know opinions on the following. And possible solutions/convincing arguments, unless I am being irrational here.
Transparently adding a database interface layer
I am currently looking for ways to optimize an application that is consuming unacceptable amounts of memory.
Backend development philosophy
I feel kind of lost in this backend development process I am attempting right now. Most of the usual development practices I use while developing client-side applications don’t apply here… Let me provide some context.
Backend development philosophy
I feel kind of lost in this backend development process I am attempting right now. Most of the usual development practices I use while developing client-side applications don’t apply here… Let me provide some context.
Backend development philosophy
I feel kind of lost in this backend development process I am attempting right now. Most of the usual development practices I use while developing client-side applications don’t apply here… Let me provide some context.
Backend development philosophy
I feel kind of lost in this backend development process I am attempting right now. Most of the usual development practices I use while developing client-side applications don’t apply here… Let me provide some context.
Pipeline-like calculations with intermediate files: should I use a build system?
I have seen multiple examples of systems that are organized essentially like a pipeline. Each stage produces some intermediate files which are then consumed by the next stage. Also, these take a long time and contain custom code, shell scripts and everything else imaginable (as opposed to everything neatly written in programming language X).