RFR: 8221397 Support implementation-defined Map Modes
adinn at redhat.com
Tue Apr 9 12:55:19 UTC 2019
On 09/04/2019 13:47, Alan Bateman wrote:
> On 08/04/2019 15:05, Andrew Dinn wrote:
>> Hmm, yes that's an interesting point. Of course, I'll take whatever
>> suggestions you are willing to throw this way :-)
> What would you think about not promoting the constructor to public? The
> original motivation for that was to be able to create additional map
> modes in jdk.internal.misc.ExtendedMapMode but we can use shared secrets
> or other skullduggery to do that. The advantage is that we avoid
> creating expectation in the API that developers can create their own map
> modes. The rest of the solution doesn't change, it's just eliminating
> the ability to create modes beyond the standard and extended modes.
I'm happy to skulldig if you provide the advice on how to do it (an
Idiot's Guide to Trepanning?). It definitely sounds better to expose
this in a controlled way rather than via a general API.
Can I assume this will remove the need for a CSR?
Senior Principal Software Engineer
Red Hat UK Ltd
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander
More information about the core-libs-dev