-
assigned issue to
Weave All should use same order as when reusing
Issue #270
resolved
The order of weaving when reusing a concern is level-respecting, i.e., bottom-up and merging instantiations for the same aspects. This ensures that each aspect is only woven once, which makes it easier to deal with duplicates.
When using "weave all" inside the tool, either to compose the final application or seeing the result of a concern design, the same weaving procedure should be used.
Comments (2)
-
reporter -
reporter - changed status to resolved
Merged into master in pull request #42.
- Log in to comment