(cherry picked from commit 1fd9957b)

(cherry picked from commit 4de6848e)

(cherry picked from commit b6b00a93)

(cherry picked from commit b72f5b8a)

Add support for Input() and Output() (available in Chisel2 since ucb-bar/chisel2-deprecated#734) and test for same.

(cherry picked from commit 8f96e509)

Documentation for example had parameters in wrong order, and was missing @param. Additionally, it was lacking a module wrapper. This has been corrected.

(cherry picked from commit e564fff1)

Signed-off-by: Schuyler Eldridge <schuyler.eldridge@ibm.com>
(cherry picked from commit 55c98cbb)

Resolves #841

(cherry picked from commit b17998ea)

(cherry picked from commit b545a4e0)

They should not be deprecated until zero-width wires actually work

(cherry picked from commit 94be48d7)

(cherry picked from commit 9591d690)

(cherry picked from commit 1fd9957b)

This reverts commit d0cdd3b4.

Fixes #763
Add tests for #763 and #472

This has a few implications
* Constructing a literal no longer increments _T_ suffixes
* Internally, wrapping a literal Bits in Node(...) will work
* Literal Bools work in withReset/withClockAndReset

The Vec constructor invokes the gen argument for each element in the
Vec. Since VecInit invokes cloneSupertype which touches every element of
the input Seq, this was an n^2 operation. Vec.apply accepts its
arguments by value so cloneSupertype is only called once. It then calls
cloneType on that once for each element in the Vec, which is constant
time reducing the overall complexity of VecInit to just n.

* Add test for UIntToOH

* Pad UIntToOH inputs to support oversized output widthds

* Optimize Bits.pad in case of known widths

* Add missing import and fix test in OneHotMuxSpec

They should only be instantiated through their companion objects.

Resolves #815

Resolves #809

If autoclonetype is unable to determine an outer class, this attempts to insert a null (and give a deprecation warning), preserving old behavior (in some cases) where the new behavior doesn't work.

This doesn't provide full compatibility with old autoclonetype: this does not attempt null insertion in the general first argument (if it's not an outer class reference). Reasoning is that inserting a null for an explicit argument is probably not the right thing to do, and will likely cause a difficult-to-debug NullPointerException (whereas that would be unlikely for an outer class, which is not always referenced in Bundle subclass code).

PiperOrigin-RevId: 187258707

SyncReadMem.read with an enable signal currently only works in
compatibility mode, where Wires are implicitly initialized to
DontCare.  Fix by explicitly assigning DontCare to the Wire.

This might fix #775.

# Conflicts:
#	build.sbt
#	project/build.properties

Makes Builder.updateBundleStack a bit stricter in deciding how many stack frames to discard by additionally matching against method names and deleting stack frames at or above the frame currently being inserted.