chipsalliance/chisel

RFC: Deprecate either Decoupled or DecoupledIO?

オープン

#2,463 opened on 2022/03/28

 (12 件のコメント) (1 件のリアクション) (0 人の担当者)Scala (651 件のフォーク)batch import
good first issue

Repository metrics

Stars
 (4,658 個のスター)
PR merge metrics
 (平均マージ 3d 21h) (30d で 16 merged PRs)

説明

Type of issue: feature request

Impact: API modification

Development Phase: proposal

Other information

If the current behavior is a bug, please provide the steps to reproduce the problem:

What is the current behavior?

User does something like:

val foo: DecoupledIO[Bar] = Decoupled(bar)

There is a mental burden to remember which one is DecoupledIO and which one is Decoupled, for no good reason.

What is the expected behavior?

User would write:

val foo: Decoupled[Bar] = Decoupled(bar)

OR

val foo: DecoupledIO[Bar] = DecoupledIO(bar)

We'd deprecate the other one for a version or so.

Similar for ReadyValids and such, I didn't do a comprehensive survey

Please tell us about your environment:

What is the use case for changing the behavior?

Less mental load for users.

コントリビューターガイド