chipsalliance/chisel

RFC: Deprecate either Decoupled or DecoupledIO?

開放

#2,463 建立於 2022年3月28日

 (12 則留言) (1 個反應) (0 位負責人)Scala (651 個分叉)batch import
good first issue

倉庫指標

星標
 (4,658 顆星)
PR 合併指標
 (平均合併 3天 21小時) (30 天內合併 16 個 PR)

描述

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.

貢獻者指南