There are also bits of runtime trickery that we can use to allow the compatibility interfaces to only be defined if you import the compatibility namespace. Notably we'd need our own@implementerfor that, which could conditionally import the underlying@implementer. We would probably want this so ...
ImmutableList.Builder<String> commands = ImmutableList.builder();// It would be great if we could use BashCommands.setHostname(), but it doesn't quite do what we need: it// maps the hostname to 127.0.0.1. But this then means that e.g. "ping myhostname" pings 127.0.0.1, and that...
#include <cassert>[[maybe_unused]]voidf([[maybe_unused]]boolthing1,[[maybe_unused]]boolthing2){[[maybe_unused]]lb:// the label “lb” is not used, no warning[[maybe_unused]]boolb=thing1&&thing2;assert(b);// in release mode, assert is compiled out, and “b” is unused// no...
After a bit more thought, I think it should be evident that this calculationcannotbe done in the hermitian-symmetry output space of a R2C transform. Hermitian symmetry has a specific meaning, and it does not mean that the output values that aren’t formally represented are zero...
import time from mlq.queue import MLQ # Create MLQ: namespace, redis host, redis port, redis db mlq = MLQ('example_app', 'localhost', 6379, 0) job_id = mlq.post({'my_data': 1234}) result = None while not result: time.sleep(0.1) job = mlq.get_job(job_id) result = job['...
Pretty soon we'll have to start just taking OSDs completely out of the cluster, zapping the disk, and then readd back to the cluster. We have over 100,000 OSD maps stored on each OSD and we're using about 10% of our raw disk space to store these maps so its quickly becoming a ...
I was originally tempted to blame some of the perceived slowness on JIT warmup, but I’m not sure that’s likely. I’ve started experiencing JIT warmup more frequently myself, as I’ve been using PyPy more. PyPy is a JITted Python implementation (written in itself, hence the name), ...
I was originally tempted to blame some of the perceived slowness on JIT warmup, but I’m not sure that’s likely. I’ve started experiencing JIT warmup more frequently myself, as I’ve been using PyPy more. PyPy is a JITted Python implementation (written in itself, hence the name), ...
NodeUtil.newQName(compiler, basePath + prop.name.getString()));// If a property string is quoted, make sure the added prototype properties are also quotedif(prop.name.isQuotedString()) {continue; } propertyNode.useSourceInfoIfMissingFromForTree(prop.name); ...
namespace X265_NS { #endif static const char short_options[] = "o:D:P:p:f:F:r:I:i:b:s:t:q:m:hwV?"; static const struct option long_options[] = { { "help", no_argument, NULL, 'h' }, { "fullhelp", no_argument, NULL, 0 }, ...