How to clone a Windows Runtime map in the face of possible concurrent modification, part 2
The article discusses the process of cloning a Windows Runtime map in the presence of potential concurrent modification. The author explains that they have previously developed a function that performs the cloning, but they are now exploring alternative designs for the function.
The author suggests breaking the cloning process into two separate functions, one for using a std::map
and another for using a std::unordered_map
. This approach avoids potential issues when the original function is called with incompatible types.
The article then delves into the implementation details of a worker function that clones the Windows Runtime map into a C++ vector of IKeyValuePair
objects. The author also introduces several helper functions to simplify the process of type deduction.
The article concludes by mentioning that the next step is to port the code to C++/CX.
This article provides valuable insights for developers working with Windows Runtime maps and offers alternative approaches to cloning them. The author's explanations and code examples make it easier for developers to understand and implement the cloning process in their own projects.