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.
Clang has a 6 month release cadence, and the last few years we've updated to an even release in the fall (#4991, #3261, #2010). We bumped to clang 17 relatively recently (mainly due to waiting for the stdlib rollout, and then because GCC 13.3 got stuck), but IMO we can keep the previous rhythm here.
In particular, development on LLVM 17 has stopped completely. The same is true for LLVM 18 actually, but at least it contains 6 months more of features & fixes. Upstream is currently doing point-releases for 19.x, which will stop with the release of v20 early next year. We can then do a bump to GCC 14 & Clang 19 in the spring again (after the release of GCC 15 resp. the corresponding 14.x point-release).
To-Do list based on docs
__int128
arguments are passed (this was a long-running effort by the Rust folks AFAIU)Previously: #4890 #4991 #4215 #3731 #3290 #3261 #2802 #2010