Unexpected behavior for `filepath.join("/","one")`
Open
Nobody has claimed this yet.
- Dominant language
- Gleam
- Stars
- 34
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
I would expect this at least for Linux & OSX:
should.equal(filepath.join("/","one"),"/one")
At least those will give that same result:
- Go
path/filepathwithfilepath.Join("/", "one") - Python
os.path.join("/", "one") - Rust
Path::new("/").join("one")
Contributor guide
No contributing guide indexed for this repository
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 locating the implementation of filepath.join and any existing tests for joining absolute paths. Reproduce the issue's Linux and OSX example, then add a regression test covering filepath.join("/", "one") and verify that it returns "/one".
Written by the indexing model from the issue text.
Assessment
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100