Bring back clonefile on Mac OS X
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 399
- Forks
- 11
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
Part of the reason why bun install is almost instantaneous is because of the use of clonefile, which implement a copy-on-write mechanism, actually avoiding the writes to disk altogether.
We exposed this via libuv some time ago, but this behavior was reverted in https://github.com/libuv/libuv/pull/3987.
cc @santigimeno @cjihrig
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read libuv pull request 3987 first, then trace the prior exposure of clonefile described in this issue. Done means restoring clonefile-backed copy-on-write behavior for macOS while retaining support on other platforms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- operating-systems, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100