Closed abferm closed 4 years ago
Is this a major "there be dragons lurking about" problem that would preclude it from being used in "production" code?
I ask because many months have passed with no feedback on this issue, where the shown results should warrant some sort of response by the library stewards.
After seeing this, I'm a little hesitant wiring it in to some current projects I'm working on where it would make a good fit.
I am currently using goflow in some production code, working around some of its inherent issues. It makes heavy use of reflect which is highly discouraged by most of the golang community. I have a fork that I would like to refactor to be more "go like", but have not had the time to do so.
I wrote a toy web spider using this package and had nothing but issues with race conditions. If only I had run go test on this package first.
Closing this as legacy
. The current master
branch is tested with -race
as part of CI.
Output of
go test -v -race
, I can't even get the tests to finish executing.