We use the library in a server and don't want to have file descriptors leaking.
The way I implemented it now changes the API so it may not be welcome. We could instead add a NewReaderAtCloser() (*ReaderAtCloser, error) function. The ReaderAtCloser could embed a Reader and thus offer the same functionality without changing the API for existing users.
We use the library in a server and don't want to have file descriptors leaking.
The way I implemented it now changes the API so it may not be welcome. We could instead add a NewReaderAtCloser() (*ReaderAtCloser, error) function. The ReaderAtCloser could embed a Reader and thus offer the same functionality without changing the API for existing users.