Markus Zimmermann

go-leak works with very very old versions of Go. So if you want to port it to newer ones: go for it!

Hey. As many might have expected i am super swamped with my "day"-job at @symflower and having a kid takes up all my private time. I did not work out...

Are you using windows?

I am really sorry but I do not have a Windows machine to try to solve this. Can you help me?

@afraca: The usual workflow I use when I fork a project for doing a PR to said project is: Checkout the project in the correct subdirectory (e.g. ~/go/src/github.com/zimmski/go-mutesting on my...

@afraca: The osutil problem should be already solved. So please give it another whirl!

@afraca: The "no-exec" option should generate all mutations for the given package(s) but should not execute any test suite. I tried the "no-exec" option with `go-mutesting --verbose --no-exec github.com/zimmski/osutil/...` I...

This is a hard problem which I have with other analysis tools too. I think it would be better to utilize a generic solution instead of hardcoding this into go-mutesting.

The problem is that the blacklisting cannot be marked in the source code, since it is mutation specific, and there can be many mutations for the same source code line....

We (@symflower) have the same problem: sometimes "no such file or directory" is returned as an error for LockFile.TryLock. The change provided by @bboreham fixes that (THANKS!). Here is a...