Skip to content

Switch from Clang 14 to Clang 16 #5369

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 9 commits into
base: develop
Choose a base branch
from
Draft

Switch from Clang 14 to Clang 16 #5369

wants to merge 9 commits into from

Conversation

bthomee
Copy link
Collaborator

@bthomee bthomee commented Mar 27, 2025

High Level Overview of Change

This change switches from Clang 14 to Clang 16.

Context of Change

Clang 14 has not been in development since 2022, and it is lagging in C++ 20 that we now commonly use. Antithesis also requires Clang 16 and the corresponding CI pipeline requires building from scratch for that compiler. With this switch we optimize our CI time and ensure we are ready for more modern C++ versions.

Type of Change

  • Refactor (non-breaking change that only restructures code)

Copy link

codecov bot commented Apr 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.0%. Comparing base (e429455) to head (5ca72a9).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff            @@
##           develop   #5369     +/-   ##
=========================================
- Coverage     78.1%   78.0%   -0.1%     
=========================================
  Files          795     795             
  Lines        68567   68663     +96     
  Branches      8286    8375     +89     
=========================================
- Hits         53545   53540      -5     
- Misses       15022   15123    +101     

see 98 files with indirect coverage changes

Impacted file tree graph

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant