Add the `unlink` benchmark, including its specification, implementation, proof, and GNU comparison tests, within the scope below. | Question | Answer | | --- | --- | | Where is the GNU code? | unlink.c: main | | What must I implement? | Exactly one operand, including symlink operands. | | What must the spec guarantee? | One FilesystemUnlink request without terminal dereference; preserve the returned state and select GNU failure diagnostic. | | Which APIs can I use? | Typed filesystem request/result calls selected by this entry; path/kind queries where needed, output outcomes and diagnostics. | | What is outside this task? | Recursive removal and open detached handles. | Source paths in the table are relative to `coreutils/src/`. See [implementation notes](https://github.com/prosyslab/dafnyutils/blob/7b481114ea5fd4a787f4dc1e587d17e8ee10b6a8/docs/implementation-notes.md#unlink), [common implementation rules](https://github.com/prosyslab/dafnyutils/blob/7b481114ea5fd4a787f4dc1e587d17e8ee10b6a8/docs/implementation-notes.md#common-implementation-rules), and the [contribution workflow](https://github.com/prosyslab/dafnyutils/blob/7b481114ea5fd4a787f4dc1e587d17e8ee10b6a8/CONTRIBUTING.md#extending-benchmark).
Activity
duncan020313 commentedon Oct 20, 2026
Resolved by #39.