-
Notifications
You must be signed in to change notification settings - Fork 9
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
@safe
setter for driver
#15
Comments
You may be able to migrate the open files as well, if you pull them out of the current driver as file descriptors, and open them in the new driver. |
That meant keeping track of all open files within the driver, not a reasonable option. Also driver changes don't seem to have a use-case. |
I actually meant manually, not automatically . I’m thinking of the standard handles which you don’t want to close. |
Regarding changing flags, the driver already supports opening with a file descriptor, so it has to deal with that already. |
I agree that changing drivers mid-program doesn't really have a great use case. However, it should be supported on entry to |
btw, you can store shared driver in TLS: struct LocalShared(T)
{
shared T value;
alias value this;
}
LocalShared!Driver _driver; |
Track number of open files/sockets in driver to allow
@safe
setting/swapping of the IO Driver.The text was updated successfully, but these errors were encountered: