SQLite Forum

Kind request: Please make SHA3/? part of built-in functions
Login
> Why then not incorporate this (SHA3) and all other 'official' extensions in the amalgamation code, disabled by default yet easily available to enable with a simple turn of a compile time define 'switch'?

Because then *any* bugfix/enhancement of *any* extension would require publishing an entirely new amalgamation. Would you want to have to track which releases affect the particular extensions you use, and which don't?