nim reported a new issue against the project: `golist` that you are following: `` Because the naming of Go projects is a mess many of them (including core Google modules) have started asserting how they should be named.
This results in golist panics.
Because golist is often called by other scripts (for example, rpm dependency scripts) the panic messages are unhelpful, because the recipient of those messages has not called golist directly and does not know what exact golist call resulted in this panic.
golist should handle this case by default and: 1. output useful info to stderr, including what exactly it was doing at the panic time 2. abort with an error code ``
To reply, visit the link below or just reply to this email https://pagure.io/golist/issue/14
qulogic added a new comment to an issue you are following: ``
This results in golist panics.
Do you have an example package of this panic? ``
To reply, visit the link below or just reply to this email https://pagure.io/golist/issue/14
golang@lists.fedoraproject.org
-
Elliott Sales de Andrade -
Nicolas Mailhot