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.

贡献者指南