AFNix galaxy code search #88
Labels
No labels
Compat/Breaking
Difficulty/Architectural
Difficulty/Easy
Difficulty/Hard
Help Wanted
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Security
Silenced Alert
Status/Abandoned
Status/Blocked
Status/Need More Info
Status/Postponed
Tracking Issue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: afnix/infra#88
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We want a code search as web interface for nixpkgs and potentially more projects, so developers can easily find code and reference it using a link.
A few months ago, source graph would have been basically the no-brainer solution, but they switched to a closed source license.
We have a few options here:
@jade suggested we could ask source graph to sponsor us a license. I personally would prefer to go with a FOSS solution to reduce our reliance on third parties.
TODO:
i think most likely the only viable option of that list is searchfox. the others do not have precise code intelligence support which should be a non starter. ctags on web is just so silly.
@jade could you expand on the precise code intelligence support that searchfox has? I was not able to find any information on that on searchfox (but it is likely that I missed it)
You may observe that it has very consistently correct c++ navigation. this is due to the clang plugin they use. I've not done much more research other than seeing there's a clang plugin, though.
From what I can see it will not work on nix files, unless a specific plugin is written
In the ideal world, a tool should use https://lsif.dev/ so we can provide a Nix LSIF.
(or https://sourcegraph.com/blog/announcing-scip but unsure.)
Yes, though this is the status quo exactly, nobody has precise code intelligence for nix files. It's possible to dump an export of most NixOS option locations though, which we could use to start building a precise code intel system of some kind possibly. or at least put some stuff into the index usefully idk.
The other mentioned systems seem so deeply unserious that they are just ctags and one won't expect any precise code intel in them at all.
We still want this for the galaxy of AFNix projects.