Comment relevant for all 3 PRs: this is handy to have in upcoming 1.2.2 (if so, process is rebase the PR to be against v1.2-histrionicus branch), or this is good for 1.3.0?

Regarding the tests, I would think it makes sense, probably to be added in https://github.com/duckdb/duckdb/blob/main/.github/workflows/NightlyTests.yml, these are run once per day and then failures are flagged to relevant team member.

Thanks.

• Happy to rebase and retarget the PRs.

• Are there other branches to be aware of?

• Who can help specify the tests? Are you expecting additional input from me?

1. rebase I think just makes sense here, thanks
2. no, after merge on 1.2-histrionicus branch they will be merged onto main
3. on testing, I saw that adding cppcoreguidelines-init-variables to clang-tidy check (via changing .clang-tidy file) flags a bunch of other stuff, unsure if that's too noisy. Or better would be set up a test that is as close as possible, basically a copy of https://github.com/duckdb/duckdb/blob/main/.github/workflows/NightlyTests.yml#L205 removing the 32bits details and adding the relevant CMAKE_CXX_FLAGS / CMAKE_C_FLAGS added to cmake invoke, since those are passed down correctly

On testing, @Mytherin to make a call on how to move forward. Thanks

Thanks!

We do run these warnings - I think the main thing is the compiler version. We could consider running these checks also with a newer compiler.