Fix FFI section: corresponding C type name

[sogaiu]

I don't understand the details very well, but I'm curious why ptrdiff_t and not ssize_t.

Something in here, perhaps?

[iacore]

ssize_t is not in the C standard. I've not seen it in C codebase before.

https://en.cppreference.com/w/c/types

[sogaiu]

That sounds similar to the following from the mailing list post:

3. ptrdiff_t is more ubiquitous and better-standardized than ssize_t, as ptrdiff_t is required by the C standard whereas ssize_t is required only by POSIX.

I wonder if it doesn't make sense for ffi.c to use :ptrdiff instead of :ssize then...

@tr{@td{@code`:ptrdiff`} @td{ptrdiff_t}}

[iacore]

I wonder if it doesn't make sense for ffi.c to use :ptrdiff instead of :ssize then...

@tr{@td{@code`:ptrdiff`} @td{ptrdiff_t}}

We can support both :ptrdiff and :ssize (backwards compatible).

[sogaiu]

Ah, there's an idea :)

[iacore]

Question: why is float r32 not f32? Also, maybe the better name is usize and ssize. Rust and LLVM uses isize.

[sogaiu]

Question: why is float r32 not f32?

Wondered the same.

Looking at my QWERTY keyboard, I see r is quite close to f...but then I came across this.