Dimitri Tcaciuc
Dimitri Tcaciuc
I could not reproduce this with golang 1.17.5 🤔
I originally tried it on Windows11/WSL, but now I also tried it on MacOS Catalina and I still can't reproduce the issue. It's a wild guess, but could that MaxInt64...
@Maxrovr ping
Sorry, I don't really understand the last bit, is staticcheck from go-tools not working with 1.18? Errcheck doesn't really do much aside from checking if you captured the returned error....
Okay, I see. Other devs may weigh in on this as well, but I think your best bet would be to wait until the 1.18 compatibility.
Hello, Right now excluding recover() is not possible. I personally think that recover() failure is something you want to handle one way or another but, if you really want to...
I would like to second the request for supporting custom package sites. We currently use Elm in a corporate environment and our policy does not allow us to host packages...
mode/textobject.go does this by accepting range function argument and executing it after text object is fully defined on mode exit. This is used by 'd' command in mode/normal.go
> bazel in that it really does not like dealing with full paths Could you clarify what "full" path means here? Is the difficulty here not knowing where "cd" is...
Have you tried listing the function in the exclusion file? In general, this is the expected errcheck behavior. Considering the main purpose of the program, given a choice between "developer...