Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Opening a file in write mode may cause a visible side-effect #6

Open
asajeffrey opened this issue Oct 1, 2010 · 0 comments
Open

Opening a file in write mode may cause a visible side-effect #6

asajeffrey opened this issue Oct 1, 2010 · 0 comments

Comments

@asajeffrey
Copy link
Member

Currently, opening a file for writing causes it to be opened immediately, not on commit. This may cause a visible side-effect, e.g. creating or clearing an existing file. Perhaps the semantics should enforce that files are always opened as tmp files, and are copied to their destination when closed? We could save the filename in a ref to be opened on a later commit, but this would mean that Agda handles aren't Haskell handles, which complicates the FFI layer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant