RFC: split fs.lua into io-only and lfs-dependent parts #22
Labels
No labels
coordination/cross-repo
coordination/needed
effort
large
effort
medium
effort
small
meta/duplicate
meta/planning
meta/wontfix
priority
high
priority
low
priority
medium
session
blocker
session
handover
session
next
status
blocked
status
done
status
in-progress
status
review
status
to-go
type
admin
type
bug
type
config
type
deployment
type
docs
type
enhancement
type
feature
type
handover
type
infrastructure
type
installation
type
maintenance
type
migration
type
research
type
security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
DAW/daw-lua-common#22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Open question
fs.luahas two distinct dependency layers:read_file,write_file,copy,remove,rename-- only needio.open, no lfsexists,is_dir,mkdir_p,list_*,find_recursive-- require lfsOptions
fs.lua(io only) andfs/dir.lua(lfs) so hostswithout lfs can still use basic file read/write
Decision needed
Are there hosts that use fs but cannot or should not depend on lfs?
Superseded by the fs/ split done for other reasons this cycle: fs/dir.lua, fs/file.lua, fs/handle.lua, fs/temp.lua, fs/query.lua. Not an exact match for the io-only/lfs-only boundary originally proposed, but the practical goal (fs is no longer one monolithic file) is met. Closing without further action; re-open if the exact boundary from the original proposal is still wanted.