Should OsPath be (public) newtype over OsString anyway?
Open
discussion
- Dominant language
- Haskell
- Stars
- 74
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
In GitLab by @phadej on Aug 2, 2022, 19:27
I'm thinking this from the POV if there were "right" `IsString` type-class.
Currently `osp` and `osstr` quasiquoters are different, but as `type OsPath = OsString` we cannot do type-directed resolution.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the current OsPath and OsString definitions and the osp and osstr quasiquoters. Review how the existing type alias affects type-directed resolution, then establish the intended public representation and its compatibility implications before identifying the tests needed for the chosen design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100