IMHO, the options you listed still miss the point.
When I do a code-related search, most often I'm looking for a documentation entry.
So, for example, if I search for "python string replace", Google returns me a bunch of crappy pages.
I can fix it with "site:python.org string replace".
SearchCode does a terrible job [1]. So does Public WWW [2].
Now, Google nails with the first result, pointing to Python's built-in types page. But it would be perfect if it could just add a #str.replace fragment to the URL [3] and save me some scrolling. Instead, it sends me to the top of the page...
When I do a code-related search, most often I'm looking for a documentation entry.
So, for example, if I search for "python string replace", Google returns me a bunch of crappy pages.
I can fix it with "site:python.org string replace".
SearchCode does a terrible job [1]. So does Public WWW [2].
Now, Google nails with the first result, pointing to Python's built-in types page. But it would be perfect if it could just add a #str.replace fragment to the URL [3] and save me some scrolling. Instead, it sends me to the top of the page...
[1] https://searchcode.com/?q=python+string+replace
[2] https://publicwww.com/websites/python+string+replace/
[3] https://docs.python.org/3/library/stdtypes.html#str.replace