Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | joshuaspence | T4558 Make Diviner useful for third-parties | ||
| Open | None | T8533 Allow Diviner to fall back to (or link directly to) the Symbol index | ||
| Open | epriestley | T13047 Plans: Symbol Indexes | ||
| Wontfix | epriestley | T8536 Merge symbols and Diviner |
Event Timeline
I suspect it may not make sense to totally merge them -- particularly, I think the "pipe CTAGS into some script" sort of use case is valuable indefinitely.
They could definitely benefit from tighter integration, though (e.g., Diviner creates and can link to symbols).
Actually I fnd the "pipe CTAGS" use case odd. I think it would be more useful if you could just run diviner generate inside a directory and we automatically generate symbols and documentation (unless you disable one or the other perhaps). In particular, this could maybe let us generate documentation stubs for languages we don't know about.
Oh, sure, that makes sense. So maybe not "valuable indefinitely", just "valuable until Diviner can extract symbols from a bunch of languages".
Per above, I think the pathway forward here is probably "tighter integration", not "merge/replace", i.e. tools for Diviner to automatically update Symbols, too. I'm just going to conceptually roll this up into T13047.