After the recent PRs were accepted, I was worried that the C++14 branch was going to be a difficult branch to bring up to date... and in short... it was.
This PR brings the C++14 branch in line with the current master, and keeps the development that took place in this branch in tact. Most importantly, all unit tests pass, which is at least a little bit of proof that this PR doesn't break anything. :}
I feel badly about the mess that this PR might look like... with the doxygen update in the most recent PR, there were so many line changes in both branches that I had to go function by function to untangle everything.... The point to stating that here is that if this PR is accepted, the C++14 branch will warrant additional review, and additional work, to make sure all intent was met, and that the library's authors are happy that everything was carried out to their original intent.
Thank you for reviewing my work. I will be happy to address any concerns with this PR!
Hi,
After the recent PRs were accepted, I was worried that the C++14 branch was going to be a difficult branch to bring up to date... and in short... it was.
This PR brings the C++14 branch in line with the current master, and keeps the development that took place in this branch in tact. Most importantly, all unit tests pass, which is at least a little bit of proof that this PR doesn't break anything. :}
I feel badly about the mess that this PR might look like... with the doxygen update in the most recent PR, there were so many line changes in both branches that I had to go function by function to untangle everything.... The point to stating that here is that if this PR is accepted, the C++14 branch will warrant additional review, and additional work, to make sure all intent was met, and that the library's authors are happy that everything was carried out to their original intent.
Thank you for reviewing my work. I will be happy to address any concerns with this PR!
-Mark