[go-nuts] Re: Go program getting SIGSEGV as it panics and runs down after a SIGTERM or a SIGINT signal

2020-07-02 Thread Charles Hathaway
Hey Steve, I'm no expert here, but the thing that sticks out to me is the garbage collection stacks in there, which suggests things are crashing while GC is running. Does the frequency change if you adjust the garbage collection frequency? Charles On Thursday, July 2, 2020 at 2:18:31 PM UTC-7

[go-nuts] Code coverage in error cases when compared to other languages

2020-12-07 Thread 'Charles Hathaway' via golang-nuts
Hi all, I'm looking for a good study/quantitative measure of how well-written Go code looks compared to other languages, such as Java, when it comes to test coverage. In particular, how handling errors may reduce the percentage of code covered by tests in Go relative to other languages. For ex

Re: [go-nuts] Code coverage in error cases when compared to other languages

2021-02-04 Thread 'Charles Hathaway' via golang-nuts
omplexity (adding mocks) in order to achieve a higher test coverage >> (covering 'return err' line)? Would that additional coverage be useful >> given that 'return err' has no complexity and Go has the compiler/linter? >> >> Full disclosure: I'