[paldepind]

Just like how await and try are mapped to unary_expr this PR does the same for borrow, consume, copy, and unsafe expressions.

[Copilot]

🟡 Changes recommended

The new Swift unary operators lack operand value propagation in unified data flow, causing flows through borrow, consume, copy, and unsafe to stop at the wrapper and leaving a gap in security analyses.

1 open issue

• Add new unary operators to unified data flow · New

What changed in this PR

Adds unified Swift extraction support for borrow, consume, copy, and unsafe, representing them as unary expressions like await and try.

Changes:

• Adds translation rules that preserve each keyword as a prefix operator and translate its operand.
• Removes the corresponding unsupported-node mappings.
• Adds a borrow fixture and updates expected output for all four expressions.

File	Description
unified/​extractor/​tests/​corpus/​swift/​expressions/​unsafe-expression.output	Expects a unary expression wrapping the call.
unified/​extractor/​tests/​corpus/​swift/​expressions/​copy-expression.output	Expects a copy unary expression.
unified/​extractor/​tests/​corpus/​swift/​expressions/​consume-expression.output	Expects a consume unary expression.
unified/​extractor/​tests/​corpus/​swift/​expressions/​borrow-expression.swift	Adds a basic borrow-expression fixture.
unified/​extractor/​tests/​corpus/​swift/​expressions/​borrow-expression.output	Records the borrow fixture’s expected syntax trees.
unified/​extractor/​src/​languages/​swift/​swift.rs	Adds the four unary-expression translation rules.

_{Review effort: Balanced (auto)}

[Copilot]

🔵 Needs a closer look

The new wrappers propagate value flow but not operand types, causing unannotated declarations to lose inferred receiver types and breaking subsequent member or method resolution.

No open issues 🎉

1 previously missed issue

In code that hasn't changed since last review

Propagate operand types through all four copy operators

unified/​ql/​lib/​codeql/​unified/​internal/​dataflow/​DataFlowPluginSwift.qll:75

Value flow now passes through these wrappers, but neither TypeInferencePluginSwift.qll::inferType nor TypeInference.qll::stepLanguageSpecific propagates their operand types. Consequently, an unannotated declaration such as let copied = copy original loses the inferred receiver type needed to resolve subsequent instance member accesses or method calls. Propagate operand types, including generic type paths, through all four operators and add type-inference/member-resolution regression tests.

1 resolved since last review

• Add new unary operators to unified data flow

_{Review effort: Balanced (dynamic)}