Yes, please.
> On 8 Dec 2019, at 20:48, Marcel Timmerman wrote:
>
> Hi Elizabeth,
>
> Shall I file a bug report then?
>
>> I hoped that:
>>
>> $ 6 'use NativeCall; dd my CArray[uint8] $ba .= new( 255, 254, 3, 4); dd
>> $ba[0..*-1]'
>> CArray[uint8] $ba = NativeCall::Types::CArray[uint8].
Hi Elizabeth,
Shall I file a bug report then?
I hoped that:
$ 6 'use NativeCall; dd my CArray[uint8] $ba .= new( 255, 254, 3, 4); dd
$ba[0..*-1]'
CArray[uint8] $ba = NativeCall::Types::CArray[uint8].new
(-1, -2, 3, 4).Seq
would be a solution (usint "uint8" rather than "byte"), but a
On 12/8/19 8:19 PM, Fernando Santagata wrote:
It looks like a bug: the docs
(https://docs.raku.org/language/nativetypes) specify that 'byte' and
'uint8' are the same and correspond to uint8_t in C.
Substituting 'uint8' to 'byte' in your code returns the same result.
Out of curiosity, if it is
I hoped that:
$ 6 'use NativeCall; dd my CArray[uint8] $ba .= new( 255, 254, 3, 4); dd
$ba[0..*-1]'
CArray[uint8] $ba = NativeCall::Types::CArray[uint8].new
(-1, -2, 3, 4).Seq
would be a solution (usint "uint8" rather than "byte"), but alas, no, so this
feels like a bug
> On 8 Dec 2019,
It looks like a bug: the docs (https://docs.raku.org/language/nativetypes)
specify that 'byte' and 'uint8' are the same and correspond to uint8_t in C.
Substituting 'uint8' to 'byte' in your code returns the same result.
Out of curiosity, if it is something meant for the public, what native call
i
