-
Notifications
You must be signed in to change notification settings - Fork 227
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
deprecation of the stream_to constructor #706
Comments
ISTM we could make |
It's not as easy as it seems. We need a pointer to its But perhaps with some trickery in the move constructor... |
Should help with #706, though we may need move assignment as well. Finally biting the bullet and adding move construction to `transaction_focus`, which requires dealing with that backpointer from the transaction back to the focus object. I'll try move assignment next. The obvious complication there is that `m_trans` will have to become a pointer.
Just replacing my current pointer based setup with |
Please throw any testing at it that you can. I'm still a bit nervous about the way I had to |
A next step could be to support moving of more In my test I used |
Should help with #706, though we may need move assignment as well. Finally biting the bullet and adding move construction to `transaction_focus`, which requires dealing with that backpointer from the transaction back to the focus object. I'll try move assignment next. The obvious complication there is that `m_trans` will have to become a pointer.
OK, it looks pretty solid to me, it's got a test, and I've now expressly blocked any move constructors in the hierarchy that I didn't want (previously blocked by |
Hi,
I wanted to update the library to the latest version, but now I get deprecation warnings when using the
stream_to
constructor.The static factory methods do not really work for me, since stream_to is not movable, so I cannot store it in an optional.
I guess I could write a wrapper like this:(EDIT: this wrapper unfortunately does not work)
I have a database class which can only ever have 1 writer active, so I store it in an optional and keep writing incoming data until I manually commit it.
Is there a way to store the writer in an optional
without using a wrapper struct?The text was updated successfully, but these errors were encountered: