-
Notifications
You must be signed in to change notification settings - Fork 13
remove copying when invoking objects stored in sbo #24
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
base: develop
Are you sure you want to change the base?
Conversation
|
Instead of |
I'm trying that but I'm having trouble getting code like this to then compile: move_only_function<int( noex_callable ) const> f2( std::move( f1 ) );
BOOST_TEST_EQ( f2( c ), 1235 );
move_only_function<int( noex_callable )> f3( std::move( f2 ) );
BOOST_TEST_EQ( f3( c ), 1235 );The compilers reject it with: The problem being there's no conversion from: int (*)(const boost::compat::detail::storage&to int (*)(boost::compat::detail::storage&Many of the tests fail like: Do you want me to push up my WIP branch? The more I think about it, the const_cast is probably harmless here anyway because we correctly apply the cv-ref qualifiers at the invoke site. I'm not sure what we should do to fix these kinds of function pointer cast errors. |
|
Ah, I see. Fewer const_casts will be needed if you declare the functions to take |
a68b9b4 to
eed8de3
Compare
Resolves: boostorg#23 Right now the invoke holders take the storage by-value which is strictly incorrect when using SBO as it creates a copy of the callable which leads to surprising results in user-code that expect multiple calls to a lambda with a mutable capture. Signed-off-by: Christian Mazakas <christian.mazakas@gmail.com>
eed8de3 to
d9faeab
Compare
| #endif | ||
|
|
||
| #ifdef _MSC_VER | ||
| #pragma warning(disable: 4789) // false buffer overrun warning in test_mutable_lambda() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the buffer overrun warning?
|
Can you please structure this as: commit 1 - test additions without the 4789 warning suppression; commit 2 - changes to the implementation; commit 3 - warning suppression in the test? |
Resolves: #23
Right now the invoke holders take the storage by-value which is strictly incorrect when using SBO as it creates a copy of the callable which leads to surprising results in user-code that expect multiple calls to a lambda with a mutable capture.