Re:Announcing Rust 1.19
by kibwen on Thursday July 20, 2017 @02:11PM
(#14814961)
As other commenters have mentioned, the demand here is almost all due to the desire for smoother interoperation with C code. What's gone unsaid so far is that, despite still requiring the `unsafe` keyword for many operations, this feature helps make Rust code more safe when calling into C, because it simplifies the interface and eliminates the need for hacked-up handwritten workarounds. IOW, a little bit of standardized unsafety to replace a larger amount of bespoke unsafety.
[ Parent
| on HN ]
Re:Announcing Rust 1.19
by Manishearth on Thursday July 20, 2017 @02:39PM
(#14815173)
FWIW the hacked up workaround that bindgen uses is _beautiful_
https://github.com/servo/rust-bindgen/blob/master/tests/expe...
Basically, if you have a union of A, B, C, you create a struct with three zero-sized fields using BindgenUnionField<A>, and then add a field after that containing enough bits to actually fill out the size. Because the BindgenUnionField is zero sized, a pointer to it is a pointer to the beginning of the struct, and it has an accessor that treats the pointer as the contained type.
This makes the API for field access `union.field.as_ref()` instead of `union.field`, but that's still pretty clean.
It's still a hack, and I'll be happy to see it go, but it's a really fun hack.
If only English already had a word for "beautiful, yet reprehensible". :)
Well "awful" etymologically means "inspiring awe"...
sirenlike
You know this word in another language?
Re:Announcing Rust 1.19
by andrewflnr on Friday July 21, 2017 @01:18AM
(#14818238)
There must be one in German. :)
Probably just the concatenation, like beautifulyetreprehensible.
>Because the BindgenUnionField is zero sized, a pointer to it is a pointer to the beginning of the struct
Is that a stable assumption?
Re:Announcing Rust 1.19
by Manishearth on Friday July 21, 2017 @01:51AM
(#14818354)
Because it's repr(C) IIRC yes.