Yonder Blue
Yonder Blue
I should note that I see the argument that doing the second cache check should always be fast enough not to warrant the skip. So feel free to close :)
Would be interested too :)
That is understandable. How about then splitting out into individual linters so that golangci-lint's existing scope and features could be used for each?
> in other words, use `//nolint:blah` instead of `//revive:disable:blah` Sorry I must have missed that support, or am trying it wrong? `golangci-lint` gives me for example: ``` apkg/afile.go:125:3: unhandled-error: Unhandled...
@im7mortal This page by github is nice and concise in their bulleted points of each: https://choosealicense.com. An (albeit dated) article from github shows most choose MIT https://github.blog/2015-03-09-open-source-license-usage-on-github-com.
It is often a big blocker for companies that wish to use the code, would highly recommend changing it if you want more widespread use.
Much appreciated!
No problem, let me know though (maybe create a sticky issue) if the repo is meant as a once-a-time thing and you don't want contributions. I see little clock-pro Go...
If the intent is to add some documentation, perhaps it can go in a docs folder (unless Sharing means something?) and then shown in the readme?
So are you suggesting the output be in actual C#, or serialized C#? In the readme I was hoping there might be some tools out there that can highlight source...