On Wed, 18 Nov 2020 10:08:20 GMT, Maurizio Cimadamore
wrote:
>> The current memory segment implementation defines a hierarchy with 3
>> concrete classes: one for heap segments, one for native segments and one for
>> mapped segments.
>>
>> Since there can be many kinds of heap segments (e.g. c
> The current memory segment implementation defines a hierarchy with 3 concrete
> classes: one for heap segments, one for native segments and one for mapped
> segments.
>
> Since there can be many kinds of heap segments (e.g. created from a byte[] or
> from a float[]) the current implementation
On Tue, 17 Nov 2020 14:55:07 GMT, Maurizio Cimadamore
wrote:
> The current memory segment implementation defines a hierarchy with 3 concrete
> classes: one for heap segments, one for native segments and one for mapped
> segments.
>
> Since there can be many kinds of heap segments (e.g. create
On Tue, 17 Nov 2020 14:55:07 GMT, Maurizio Cimadamore
wrote:
> The current memory segment implementation defines a hierarchy with 3 concrete
> classes: one for heap segments, one for native segments and one for mapped
> segments.
>
> Since there can be many kinds of heap segments (e.g. create
The current memory segment implementation defines a hierarchy with 3 concrete
classes: one for heap segments, one for native segments and one for mapped
segments.
Since there can be many kinds of heap segments (e.g. created from a byte[] or
from a float[]) the current implementation is prone to
