Proposal: sub-packages to enable optional features #1134
+13
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A common pain point when using go-sqlite3 is that enabling optional features requires adding a build tag to all
go
command invocations. For instance, when a program depends on FTS5, it's no longer possible to rungo build
,go test
, etc as usual. End users need to explicitly add-tags sqlite_fts5
every time.Here is a proposal to improve this. A new
fts5
sub-package is introduce. Any program which depends on FTS5 can import it to turn on FTS5:What do you think?