Hi Stanislav, yes please, file and assign to me.
Best, Michael > Am 18.05.2016 um 12:52 schrieb stanislav lukyanov > <stanislav.lukya...@oracle.com>: > > Hi Michael, > > I've noticed that neither the new method nor its friends, arrayElementGetter > and arrayElementSetter, > discuss the invocation-time behavior. > It seems important since there are exceptions to be documented. > > I think the best way would be to make a connection between the methods and > corresponding instructions, > so as not to explain every NPE and, especially, ArrayStoreException in > Javadoc. > Probably no need to go deep in details on how, for example, > arrayElementGetter(T) maps on 8 Taload instructions, > but just give a basic notion of that. > > WDYT? Should I file a separate RFE for that? (for arrayElementGetter/Setter? > for all three?) > > Thanks, > Stanislav > > On 18.05.2016 10:52, Michael Haupt wrote: >> Dear all, >> >> please review this change. >> RFE: https://bugs.openjdk.java.net/browse/JDK-8156915 >> Webrev: http://cr.openjdk.java.net/~mhaupt/8156915/webrev.00/ >> >> Thanks, >> >> Michael >> > -- <http://www.oracle.com/> Dr. Michael Haupt | Principal Member of Technical Staff Phone: +49 331 200 7277 | Fax: +49 331 200 7561 Oracle Java Platform Group | LangTools Team | Nashorn Oracle Deutschland B.V. & Co. KG | Schiffbauergasse 14 | 14467 Potsdam, Germany ORACLE Deutschland B.V. & Co. KG | Hauptverwaltung: Riesstraße 25, D-80992 München Registergericht: Amtsgericht München, HRA 95603 Komplementärin: ORACLE Deutschland Verwaltung B.V. | Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Nederland, Nr. 30143697 Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher <http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment
