Re:Profiling Go Applications with Flamegraphs
by zxcmx on Monday March 12, 2018 @05:52AM
(#16567035)
I didn't look at the file but I find that perfectly comprehensible. I can see read & write pointers in a buffer, n as bytes copied. Not sure if p is source or dest w/out looking but my guess is dest?
Maybe it's a cultural thing - lots of C code looks like this from Lion's UNIX book onwards. I still find this style easier on the eyes when it's clear from context what is going on.
For i/o code this is about as obscure as using "i" for a loop index.
Maybe it's a cultural thing - lots of C code looks like this from Lion's UNIX book onwards. I still find this style easier on the eyes when it's clear from context what is going on.
For i/o code this is about as obscure as using "i" for a loop index.