Revert "Make uselessly public fields in utils private"

[azidar]

At the bequest of @jackkoenig, this reverts commit c279860.

Type of change: other enhancement

Impact: API addition (no impact on existing code)

Development Phase: implementation

Release Notes

To properly name private and protected fields in chisel3.util.Arbiter and chisel3.util.Decoupled with the @chiselName macro annotation, these fields were made public, and thus retain a better name.

[jackkoenig]

For historical context, see #407

The private vals were named long ago, but at some point that broke. I think it's worth considering addressing #1410 at some point, but the more important goal is having these fields named in the Verilog.

[jackkoenig]

Should we backport this?

[ucbjrl]

Re: backporting - is there any chance previously private names may now collide with user/client definitions? I would hope not, but I vaguely remember that accessibility (private vs public) did interfere with visibility (inheritance uniqueness), despite the hope that it wouldn't.

[jackkoenig]

Re: backporting - is there any chance previously private names may now collide with user/client definitions?

Good point, yeah this would fail the binary incompatibility check so we shouldn't backport. 3.3 will be out soon so we'll just tell people to upgrade to get the fix.