$ go version
go version go1.12.7 darwin/amd64
$ uname -a
Darwin WudeMacBook-Pro.local 18.6.0 Darwin Kernel Version 18.6.0: Thu Apr
25 23:16:27 PDT 2019;RELEASE_X86_64 x86_64
I read a asm code segment recently, it look like this:
mov %fs:-8, %RCX // load G descriptor from TLS
cmp
On Sat, Aug 10, 2019 at 4:57 PM joe mcguckin
wrote:
>
> Is there a recommended usage for either style?
>
> Take ListenPacket for example. There a (*ListenConfig).ListenPacket version
> and a version that takes arguments.
>
> What's the difference and what is the desired usage of either?
Function
Is there a recommended usage for either style?
Take ListenPacket for example. There a (*ListenConfig).ListenPacket version
and a version that takes arguments.
What's the difference and what is the desired usage of either?
Thanks,
Joe
--
You received this message because you are subscribed to
I think I can handle the deadly embrace problem. The locks distribute into
"slots" based upon inode%slotCount. Just information irrelevant to the
observation. At the moment, I use RWMutex to protect each lock table slot
since it was more like previous thoughts on this subject. However, I plan
to co
You're absolutely right. I just meant that the tokenizer interface wouldn't
be completely replaced. There are still some corner cases where it will be
necessary.
On Friday, August 9, 2019 at 11:41:17 PM UTC+2, burak serdar wrote:
>
> On Fri, Aug 9, 2019 at 3:32 PM Jonathan Hall > wrote:
> >
But when I think about it maybe it is a better practice to only give a
leayer2 error message up a singe layer and handle it there.
And if needed only propagate a layer1 error message futher up.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
