WebAssembly / WebAssembly/WASI
Clarify what happens when you open a symlink with NOFOLLOW
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
The spec should say what happens when you try to open-at a path whose last component is a symlink, when passing empty PathFlags. POSIX 2008 specifies ELOOP (ErrorCode::Loop), which is what we get on Linux and OpenBSD. FreeBSD deviates from POSIX and returns EMLINK. No idea what the Windows solution is.
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
Start by reading the open-at specification and the definition of empty PathFlags, then compare the POSIX, Linux, OpenBSD, FreeBSD, and Windows behavior described in the issue. Done means the specification states the last-component symlink behavior and documents the platform-specific result, including the unresolved Windows case.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100