-
Notifications
You must be signed in to change notification settings - Fork 81
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
Non-copyable types of elements are not supported #22
Comments
Do you have compilation or execution problems with following code sample? I can't check it right now. |
It produces compilation error. In the code:
The error message is:
As I see it, Another similar issue here is that lambda wants to return It seems to me that working with the references would work here. I'm not sure though as I had no chance to get the lib working with references. |
@AStepaniuk some methods work by copying elements in data structures like set/map. How do you think to deal with them? |
@AStepaniuk just rolled out new version |
Will this ever be solved here? |
@Gargony not sure, any ideas on the solution? |
@k06a I solved it through std::ref
Here you cannot use vector, because vector not supports refs.
for changes:
|
This will not work:
I.e. conversion from the vector of the unique ptrs to the vector of raw ptrs does not work.
The vector of unique ptrs is convenient to have RAII for the collection of items, as it is suggested e.g. here http://stackoverflow.com/questions/27460377/why-is-using-vector-of-pointers-considered-bad
Also there are possible the other situations, when non-copyable elements can be used.
Would that be possible if
boolinq
is working with the references to the elements in such cases instead?The text was updated successfully, but these errors were encountered: