Interfacer
Dev tools
linter
SHOW HN2016
66points
9comments
#576of 2,264 in 2016
Top 26%of 2016 by points
How HN took it
QuietFewer than 5 comments about the project
0 positive, 1 neutral or asking, 1 mixed, 0 critical, out of 2 comments about the project.
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Useful for scanning code to spot overly specific types
From 1 comment
"I think this assumes that the most generic type is the best option? Personally, I don't think that's a correct assumption." Well, of course it isn't universally. But it's…
jerf on HN
Objections
Assumes the most generic type is always best
From 1 comment
Really neat package here. Don't let me take away from the work that's been done here (and correct me if I'm wrong) but I think this assumes that the most generic type is the best…
rickhanlonii on HN
Could be misused as a git hook enforcement
From 2 comments
Really neat package here. Don't let me take away from the work that's been done here (and correct me if I'm wrong) but I think this assumes that the most generic type is the best…
rickhanlonii on HN> But I would worry that someone would add this to, say, a git hook as way to enforce this assumption. You shouldn't. At that point there are so many more concerns I'd have with…
Goopplesoft on HN
Requests
Ideas or false positive examples to keep it conservative
From 1 comment
To add to what jerf already said - This is a linter, so it should be taken with a grain of salt. Having said that though, I'm trying really hard to make it conservative and not…
mvdan on HN
Questions
Whether interface use has runtime cost versus concrete types
From 2 comments
> One generic reason to use a specific type (heh) is to avoid resolving the interface on every use. Aren't Go interface checked at compile time? I thought only interface casting…
sudhirj on HNChecking that a value put into an interface type conforms to the interface type is done at compile time, so modulo issues with "nil" you can't have an interface type where the…
jerf on HN
Alternatives named
gometalinter
From 1 comment
"I think this assumes that the most generic type is the best option? Personally, I don't think that's a correct assumption." Well, of course it isn't universally. But it's…
jerf on HN