chipsalliance/chisel

Inconsistency with Decoupled and DecoupledIO

Offen

#2.436 geöffnet am 07.03.2022

 (1 Kommentar) (0 Reaktionen) (0 zugewiesene Personen)Scala (651 Forks)batch import
good first issue

Repository-Metriken

Stars
 (4.658 Sterne)
PR-Merge-Metriken
 (Durchschn. Merge 3T 21h) (16 gemergte PRs in 30 T)

Beschreibung

It's a source of confusion when to use Decoupled and when to use DecoupledIO -- can we just make them the same name and deprecate the inconsistent name?

Type of issue: feature request

Impact: API modification

Development Phase: request

Other information

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

No bug What is the current behavior?

You use Decoupled to create the thing but DecoupledIO is the type. This is really confusing.

What is the expected behavior?

They could both just be called Decoupled. And DecoupledIO would alias to Decoupled but pop up as deprecated.

Please tell us about your environment:

What is the use case for changing the behavior?

Less cognitive load

Contributor Guide