Intel's docs are unfortunately spartan, but the guarantees around program order is a hint that this is what it does.
4,936 karma · joined April 21, 2009
Email (ROT13™): fvzbafba ng tznvy qbg pbz
Intel's docs are unfortunately spartan, but the guarantees around program order is a hint that this is what it does.
> or (more likely) go into just some special small subsection of it reserved for non-temporal writes only.
I hadn’t heard of this before. It looks like older x86 CPUs may have had a dedicated cache.
So there’s a fundamental tradeoff between cost, inference speed, and hostable model size for the foreseeable future.
1) This alert doesn't show up at all on mobile.
2) IMO this should either affect the overall score or be displayed in search results as well, which is not currently the case: https://www.glassdoor.com/Search/results.htm?keyword=ZURU
It usually solves this in under 6 guesses. The guessing could be improved; at the moment it's random, but it could select for words with non-repeating letters to narrow down the search space faster.
I used the exact same tagline for a project open sourced in 2019: https://github.com/pachyderm/s2/
So there you go VCs, I can market as well as cloudflare. Money please!
A little while ago we were hitting yet another issue with dependencies related to version pinning at work. I tried to divine what the disparate versions mean, and came up with this flow chart from a legalistic reading of stack overflow issues [1] and the go modules doc [2]:
has the package opted into go modules (i.e. is there a go.mod?)
yes
does the repository use semver?
yes
is the major version <= 1?
yes
=> normal versioning, e.g. github.com/stretchr/testify v1.3.0
no
=> when importing, we need add /vN at the end, e.g., import "github.com/my/mod/v4", and in go.mod it will behave like github.com/my/mod/v4 v4.1.0
no
=> pseudo-versioning will be used, e.g. github.com/kolo/xmlrpc v0.0.0-20190717152603-07c4ee3fd181
no
does the repository use semver?
yes
is the major version <= 1?
yes
=> pseudo-versioning will be used, e.g. github.com/kolo/xmlrpc v0.0.0-20190717152603-07c4ee3fd181
no
=> version will be marked as incompatible, e.g. github.com/zeromq/goczmq v4.1.0+incompatible
no
=> ???
I still don't know if this is right. But that's not really the point. I think the go authors painted themselves into a corner with such an anemic initial release. Now that they're trying to address shortcomings, the complexity is blowing up to handle the very large/diverse ecosystem. It reminds me a lot of java around 1.4 when they added in generics. In the long-run it was the right move, but man was it painful.1: https://stackoverflow.com/a/57372286 2: https://github.com/golang/go/wiki/Modules
I was trying to figure out if QNX does this with `MsgSend`, as QNX is renowned for being a fast microkernel, but it wasn't clear to me. According to Animats, "There's no scheduling delay; the control transfer happens immediately, almost like a coroutine. There's no CPU switch, so the data that's being sent is in the cache the service process will need." [1] According to wikipedia, "If the receiving process is waiting for the message, control of the CPU is transferred at the same time, without a pass through the CPU scheduler." [2]
It seems like `MsgSend` circumvents the scheduler, but does it circumvent context switching to the kernel entirely too?
* As a replacement for the classic caffeine app. [1]
* To provide shortcuts for window managements. [2]
* To shutdown bluetooth on sleep. Otherwise, devices I have setup to pair with both my mac and phone will tend to pair with the mac, even though it's asleep. [3]
1: https://gist.github.com/heptal/50998f66de5aba955c00
2: https://github.com/miromannino/miro-windows-manager
3: https://gist.github.com/ysimonson/fea48ee8a68ed2cbac12473e87...
I don't have a strong opinion on whether cell phones or abortion or anything else caused the collapse in crime, but do feel like the theories you'll read about the most (assuming you're not an academic in the social sciences) are the ones that make for the most interesting headlines.
Also, you can use most memory management facilities in Rust (including reference counting) without `unsafe`.
1: https://words.steveklabnik.com/borrow-checking-escape-analys...