-
Notifications
You must be signed in to change notification settings - Fork 843
Conversation
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.
Another thoughts: how about define a trait with one()
, zero()
and let implement it for for some basic types ? Idea is to keep succinct Word::one()
Word:zero()
and let type system infer for us
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.
I tried to to have a trait for |
I tried to implement it in another PR and seems to work #1754 If new PR is acceptable I think we can close this one. |
@hero78119 Nice approach on #1754. I built on top of #1754 to get #1758, which removes the need to type hint the word. @hero78119 @KimiWu123 Can you share your opinion on #1758? |
Just different topic For unifying
Maybe we keep |
Close in favor of #1758 |
### Description to address discussion in PR #1748 ### Rationale implement OpsIdentity for word<T> so that we no longer need to type hint `::<Expression<F>>` or `::<F>` every time.
Description
Address #1746 (comment), we rename the constructors for zero word and one word.
Type of change
Contents