Windows compile fix: Be more specific about which AspectWithState to use #1528
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: There are other errors that still need to be resolved before
/permissive-
is no longer needed on Windows.Using DART (master) in a project on Windows yields the following compile error:
This is the same error mentioned in #753.
dart\common\AspectWithVersion.hpp
has two symbols forAspectWithState
. The first isdart::common::detail::AspectWithState
defined by include:#include "dart\common\detail\AspectWithVersion.hpp"
. This takes 5 template arguments.The second symbol is defined after the above
#include
asThis version takes 4 template arguments.
The problem is with the following line, Windows is using the first definition of
AspectWithState
, which is the incorrect version that requires 5 template arguments:Adding
common::
as I've done in the PR distinguishesdart::common::AspectWithState
fromdart::common::detail::AspectWithState
.Note: This has already been worked around on Windows by compiling with
/permissive-
, but I think this would still be a good addition to the codebase to make it more robust. Also there are other compile errors that occur without/permissive-
that I haven't resolved yet.Before creating a pull request
clang-format
Before merging a pull request
CHANGELOG.md