RFR 8198962: Move HeapScope/NativeScope out of public API

[Henry Jen]

Looks good.

I agree until we need extra capability beyond Scope API, we do not need to expose the implementation. I would imagine some tuning/configuration parameters for different type of Scope in the future, but we don’t need them now.

Cheers,
Henry

> On Mar 2, 2018, at 9:24 AM, Sundararajan Athijegannathan <sundararajan.athijegannathan at oracle.com> wrote:
> 
> Looks good.
> 
> -Sundar
> 
> On 02/03/18, 10:42 PM, Maurizio Cimadamore wrote:
>> Hi,
>> this change moves HeapScope/NativeScope out of the public API. The Scope interface is more than enough for clients - there's no need to expose the guts of how scopes are implemented. Instead, clients can easily create the desired scope using two factory methods in the Scope interface:
>> 
>> Scope::newNativeScope
>> 
>> Scope::newHeapScope
>> 
>> Webrev:
>> 
>> http://cr.openjdk.java.net/~mcimadamore/panama/8198962/
>> 
>> Cheers
>> Maurizio
>>