-
Notifications
You must be signed in to change notification settings - Fork 613
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Integer properties and conversion to FIRRTL. #3470
Add support for Integer properties and conversion to FIRRTL. #3470
Conversation
This is an alternative to #3469. There is more boilerplate for every new property type: instead of one line in the Converter and Property files, there are a few new lines in the IR, Converter, and Property files. But the upshot seems better: when you define your new property typeclass instance, you have to say how it converts to IR. Which means you have to add a new case object, which means you have to update the match statement in the converter. I sort of prefer this PR to #3469 , but curious what others think. |
05aec56
to
29519f7
Compare
6442aea
to
5de26ef
Compare
5de26ef
to
1a67a5d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
446a55d
to
cede5aa
Compare
Contributor Checklist
docs/src
?Type of Improvement
Desired Merge Strategy
Release Notes
The Integer property type is defined in FIRRTL spec version 3.1.0: https://github.com/chipsalliance/firrtl-spec/releases/tag/v3.1.0.
Reviewer Checklist (only modified by reviewer)
3.5.x
,3.6.x
, or5.x
depending on impact, API modification or big change:6.0
)?Enable auto-merge (squash)
, clean up the commit message, and label withPlease Merge
.Create a merge commit
.