This repository has been archived by the owner on Feb 18, 2024. It is now read-only.
FileSink
now closes the underlying writer.
#1213
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR modifies
FileSink
to, on close, close its innerFileStreamer
's owned writer. At the moment, the innerAsyncWrite
'sclose
method is not called when theFileSink
is closed.This is a minor backwards-incompatible change. While it won't affect cases where the FileSink wraps an actual file, which is generally closed when dropped, it may affect behavior when wrapping an
AsyncWrite
which expects close to be called. (In my case, that was a handle to an S3 object.)