Make plugin autoclonetype always on #1826
Merged
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.
Follow on to #1804, make the compiler plugin autoclonetype be always on and thus used in chisel3 itself.
Contributor Checklist
docs/src?Type of Improvement
API Impact
As described in the release notes in #1804 and reflected in the test change, this will cause issues for any Bundle that inherits from a Bundle in
chisel3.utilif the code is not also compiled using the compiler plugin. Thus, this change can only occur on the major version bump.Backend Code Generation Impact
Desired Merge Strategy
Release Notes
Always generate
cloneTypemethods for Bundles using the compiler plugin. This causes a binary and source incompatible change for any Chisel code that does not use the compiler plugin but extends aBundlein other code that does. All Chisel users should use the compiler plugin.Reviewer Checklist (only modified by reviewer)
Please Merge?