nim added a new comment to an issue you are following:
golist does not uses this kind or regexes it plugs directly in the Go compiler inner code
to match the Go compiler view of what's in a project. This was a deliberate choice by
Fedora Go maintainers last year, my initial macro implementation just performed regexes in
So golist results should be more correct that what you would expect naïvely from a human
file path analysis.
Unfortunately that also assumes the integration with Go compiler rules is correct and
complete. For example golist would initially parse files starting with '_', even
though the Go spec says it should not, I suppose because Google implemented '_' in
some other place of its codebase.
So basically, it's not as clear cut as that, this issue needs investigating why the Go
compiler code thinks this file is a test file, and whether this is correct WRT the Go
language spec, and not superseeded by some other exception golist does not implement.
To reply, visit the link below or just reply to this email