I regularly forget where/whether interfaces and constants exist, so I made myself this ranked & filterable search tool.
The hosted deployment covers the standard library + a few other packages, but it's built to be able to be pointed at any (internal) codebase too! Just need to build an index with more packages installed https://github.com/g-harel/gothrough
Im kinda wondering since the complete source is open and hosted and github (with current previews enabled) even has a usefull search - what is the actualy benefit?
Also if you are using goland (not everyone is i know thats why i pointed it out as second argument) you have the complete standard-lib lookup ready via the IDE.
Maybe im missing something and this is usefull but im coding go for several years now and dont see the point
That's a fair question... ultimately it's possible to get something similar using other tools, but IMO it won't be as easy. Just as a contrived example with a simple query:
The problem I really wanted to solve for myself was primarily discovery for standard interfaces. I don't write Go code as regularly as I'd like and don't have code review from a professional setting.
5 comments
[ 3.7 ms ] story [ 22.7 ms ] threadThe hosted deployment covers the standard library + a few other packages, but it's built to be able to be pointed at any (internal) codebase too! Just need to build an index with more packages installed https://github.com/g-harel/gothrough
Also if you are using goland (not everyone is i know thats why i pointed it out as second argument) you have the complete standard-lib lookup ready via the IDE.
Maybe im missing something and this is usefull but im coding go for several years now and dont see the point
https://gothrough.dev/search?q=writer
https://github.com/search?q=repo%3Agolang%2Fgo+writer&type=c...
The problem I really wanted to solve for myself was primarily discovery for standard interfaces. I don't write Go code as regularly as I'd like and don't have code review from a professional setting.