This PR extends the xct_specific_matcher rule to support identity operators (=== and !==) in addition to the existing equality operators (== and !=).

Changes

The rule now detects and suggests more specific XCTest matchers for identity comparisons:

New transformations:

• XCTAssert(val1 === val2) → XCTAssertIdentical(val1, val2)
• XCTAssertTrue(val1 === val2) → XCTAssertIdentical(val1, val2)
• XCTAssert(val1 !== val2) → XCTAssertNotIdentical(val1, val2)
• XCTAssertTrue(val1 !== val2) → XCTAssertNotIdentical(val1, val2)
• XCTAssertFalse(val1 === val2) → XCTAssertNotIdentical(val1, val2)
• XCTAssertFalse(val1 !== val2) → XCTAssertIdentical(val1, val2)

Example

// Before - these would not trigger violations
func testIdentity() {
    XCTAssert(obj1 === obj2)  // No violation
    XCTAssertTrue(obj1 !== obj2)  // No violation
}

// After - these now trigger violations with helpful suggestions
func testIdentity() {
    XCTAssert(obj1 === obj2)  // ⚠️ Prefer the specific matcher 'XCTAssertIdentical' instead
    XCTAssertTrue(obj1 !== obj2)  // ⚠️ Prefer the specific matcher 'XCTAssertNotIdentical' instead
}

Implementation Details

• Extended OneArgXCTAssert.Comparison enum with .identical = "===" and .notIdentical = "!=="
• Updated the suggestion method to handle all identity comparison combinations
• Added comprehensive test coverage for all new scenarios
• Updated rule examples to include identity operator cases
• Preserved all existing functionality for equality operators

Testing

• ✅ All identity operators properly detected and suggest correct alternatives
• ✅ Existing functionality preserved (== and != operators still work)
• ✅ SwiftLint runs on itself with no violations
• ✅ Comprehensive test coverage added

Fixes #5849.

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.