By default you are right. However you can use static analysis and tooling guardrails to reject certain classes of unsafe code automatically, and force the agent to go back to the drawing board. It might take a few tries and a tiny amount of massaging but I don't doubt it'd get there.

▲

pizlonator 5 days ago | parent [-]

If you could get there that way with Rust’s unsafe blocks then you could get there that way with C++

	▲	CuriouslyC 5 days ago \| parent [-]
		probably true. I think thing doing the heavy lifting is an adversarial loop on the generated code to red team it repeatedly before merge.