Extend support to all POSIX file types where possible
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 200
- Forks
- 85
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 2
Description
The suite currently supports directories (S_IFDIR), regular files (S_IFREG), and symlinks (S_IFLNK) uniformly across all tools and common library API calls. We should expand the suite to handle all POSIX types by adding sockets (S_IFSOCK), block devices (S_IFBLK), character devices (S_IFCHR), and FIFOs (S_IFIFO) where possible. For tools/calls where that does not make sense or more time is needed to add support, we can document the limitations, check for those types while processing, and print warnings/errors.
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
The issue names no files or tests. Start by inventorying the existing directory, regular-file, and symlink handling across the tools and common library API calls, then assess each requested POSIX type. Done means supported types are handled where practical and documented limitations produce checks and warnings or errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100