-
-
Notifications
You must be signed in to change notification settings - Fork 186
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
noexcept
move constructors for flex_vector
and other data-structures
#244
Comments
Hmmm... it does allocate memory but only the first time it is ever invoked, to allocate the initial "empty" node. We could maybe add some statics to pre-initialize the empty node... but that could cause trouble when using the data-structures in statics itself. Maybe the option 1) is the best? Not sure about how 2) would look like (what's an end node? you mean the root node?). I agree having a |
I see, it's essentially this piece of code, that does an allocation. Since the nodes are already shared between multiple flex-vectors, instead of keeping a pointer to an allocation in a static variable, one could instead keep the whole node as a static variable and return a pointer to it. 🤔 I might try that later today. |
I just noticed that the comment is slightly incorrect. |
I love the approach with a static allocation for the node. It's the cleanest approach. More comments in the PR, but thanks a lot for noticing and taking care of this! |
Issue can be close, because PR was merged. Or do we want to keep it open to track progress for other data structures? |
noexcept
move constructors for flex_vector
noexcept
move constructors for flex_vector
and other data-structures
Renamed and left it open to keep track of this for other data-structures. Thanks! |
We'd like immer::map to have nothrow move constructor and assignment as well. |
@mvtec-richter you may need to apply the same techniques as in #246 in order to ensure that the default constructor is |
I looked into making the move constructor (and move-assignment) for
flex_vector
noexcept
. This is something people (at least myself) want to ensure exception safety. Generally you want you types to be nothrow move constructible.It turns out to be not that trivial: it allocates nodes. This is similar to what the MSVC implementation of
std::unordered_map
does and it caused me a lot of pain in the past. At least theswap
operation is de facto noexcept, but not marked as such.I propose two solutions:
nullptr
to head and tail node would indicate an empty flex_vector.std::unordered_map
: store the end nodes within the object itself. This would require to replace the end-nodes with the new end-nodes during a move operation.I prefer approach 1. Any ideas or opinions? Maybe there is a good reason to not have flex_vectors move constructor and assignment noexcept.
The text was updated successfully, but these errors were encountered: