RFR: JDK-8193367: Annotated type variable bounds crash javac

B. Blaser bsrbnd at gmail.com
Thu Jan 24 13:52:00 UTC 2019

On Mon, 18 Jun 2018 at 22:09, Maurizio Cimadamore
<maurizio.cimadamore at oracle.com> wrote:
> Also, note that there's another related method: getUpperBound. This is
> *almost* like getBound() but it does few extra checks on top.
> While, I'm confident that this patch is not risky, I'm a bit worried
> that exposing yet another accessor will create confusion to clients -
> should they use Type::getUpperBound, Types::upperBound, or the new
> Type::bound/getBound?
> I wonder if we need some consolidation here before moving forward with
> the fix

Done some weeks ago:


Tier1 was OK at that time, thoughts?


More information about the compiler-dev mailing list