Skip to content

Subject: Safe changes correctly not flagged

A change that looks superficially risky is correctly left un-flagged: an internal/private-header type changed under public-surface scoping, a preprocessor-conditional false positive reconciled, or a genuinely ABI-neutral qualifier change.

12 case(s). ← back to all subjects

Cases

Case Title Verdict Category
case04_no_change No Change ✅ NO_CHANGE No Change
case118_internal_struct_field_added_scoped Internal Struct Gains a Field (Non-Public, Scoped) ✅ NO_CHANGE No Change
case119_internal_struct_field_removed_scoped Internal Struct Loses a Field (Non-Public, Scoped) ✅ NO_CHANGE No Change
case120_internal_struct_reordered_scoped Internal Struct Fields Reordered (Non-Public, Scoped) ✅ NO_CHANGE No Change
case164_preproc_conditional_field Preprocessor-Conditional Field (Build-Context False Positive) ✅ NO_CHANGE No Change
case184_internal_enum_churn_scoped Internal Enum Churn, Scoped Out by Private-Header Origin ✅ NO_CHANGE No Change
case186_c_api_pointee_const_abi_neutral C API Pointee const-Qualification Is ABI-Neutral ✅ NO_CHANGE No Change
case200_new_entry_point_instead_of_parameter_added New Entry Point Instead of a Changed Arity 🟢 COMPATIBLE Addition (Compatible)
case202_public_header_declaration_order_changed Public Header Declaration Order Changed ✅ NO_CHANGE No Change
case204_class_gained_non_virtual_method Class Gained a Non-Virtual Method 🟢 COMPATIBLE Addition (Compatible)
case206_deprecation_documented_without_attribute Deprecation Documented Without the Attribute ✅ NO_CHANGE No Change
case208_restrict_added_to_definition_only restrict Added to the Definition Only ✅ NO_CHANGE No Change