On Fri, 5 Jul 2024 14:01:59 GMT, Per Minborg wrote:
>> This PR proposes to retain the read-only state when any of the
>> `MemorySegment::reinterpret` methods is called.
>>
>> Previously, the read-only state was lost and the returned `MemorySegment`
>> was always writable regardless of the orig
> This PR proposes to retain the read-only state when any of the
> `MemorySegment::reinterpret` methods is called.
>
> Previously, the read-only state was lost and the returned `MemorySegment` was
> always writable regardless of the original segment's read-only state.
Per Minborg has updated th
On Mon, 10 Jun 2024 15:30:39 GMT, Per Minborg wrote:
>> This PR proposes to retain the read-only state when any of the
>> `MemorySegment::reinterpret` methods is called.
>>
>> Previously, the read-only state was lost and the returned `MemorySegment`
>> was always writable regardless of the ori
> This PR proposes to retain the read-only state when any of the
> `MemorySegment::reinterpret` methods is called.
>
> Previously, the read-only state was lost and the returned `MemorySegment` was
> always writable regardless of the original segment's read-only state.
Per Minborg has updated th
On Mon, 10 Jun 2024 15:12:59 GMT, Per Minborg wrote:
> > Note that `asSlice` methods also lacks a similar guarantee on read-only
> > (but the impl works fine there)
>
> Even though not mentioned in the original issue, we could add documentation
> for this here as well. Or maybe via
> https://
On Mon, 10 Jun 2024 13:45:16 GMT, Maurizio Cimadamore
wrote:
> Note that `asSlice` methods also lacks a similar guarantee on read-only (but
> the impl works fine there)
Even though not mentioned in the original issue, we could add documentation for
this here as well. Or maybe via https://bugs
On Mon, 10 Jun 2024 14:59:42 GMT, Per Minborg wrote:
>> This PR proposes to retain the read-only state when any of the
>> `MemorySegment::reinterpret` methods is called.
>>
>> Previously, the read-only state was lost and the returned `MemorySegment`
>> was always writable regardless of the ori
> This PR proposes to retain the read-only state when any of the
> `MemorySegment::reinterpret` methods is called.
>
> Previously, the read-only state was lost and the returned `MemorySegment` was
> always writable regardless of the original segment's read-only state.
Per Minborg has updated th
On Mon, 10 Jun 2024 13:18:43 GMT, Per Minborg wrote:
> This PR proposes to retain the read-only state when any of the
> `MemorySegment::reinterpret` methods is called.
>
> Previously, the read-only state was lost and the returned `MemorySegment` was
> always writable regardless of the original
