Though we include Boost JSON as a dependency for benchmarking purposes, we do not include it as part of our benchmarks currently.

Our users are often confused by the output from programs such as zip2john sometimes being very large (multi-gigabyte). Maybe we should identify and enhance these programs to output a message to stderr to explain to users that it's normal for the output to be very large - maybe always or maybe only when the output size is above a threshold (e.g., 1 million bytes?)

Describe the bug
Sometimes alias time does not work

To Reproduce

create table tst (
timestamp timestamp
)

select timestamp time from tst

Expected behavior
Result column name is timestamp but should be time

Screenshots

Environment (please complete the following information):

• Version: 6.0.2

Additional context
This is the workaround sy

Currently, there are a lot of implementations in WASM are missing; when I added support I was really just trying to get the portable implementations done, so even some obvious implementations (such as shuffle/convert-based implementations) are missing.

The WASM SIMD issue tracker has lots of great info on possible implementations; each time an instr