Open kozross opened 3 years ago
This sounds like a very, very good idea.
@Kleidukos If we go with anything, I'm in favour of SQLite. It's easy to depend on, and I know what it is and isn't capable of. It's also very robust on forward-and-backward compatibility, so we won't break existing documentation databases if we upgrade.
Clearly a wise choice.
Having to rely on GHC for linkage information is probably inevitable to some degree. However, we could store that in an embedded database, which means that future rebuilds will only need to call out to GHC for stuff that's stale.