On 06/24/2013 05:26 PM, Patrick Walton wrote:
On 6/24/13 2:14 AM, Michael Woerister wrote:
* There is the trans::adt module and the Repr enum which look very
promising. It does not provide all the information I need (e.g. it will
include generated fields, but does not explicitely specify where they
are located, just in comments (enum discriminant) or code (destroyedness
flag)). But otherwise it seems the place to go for a definite field list
of composite types.

I think adt is the place for this kind of thing. Feel free to add additional functionality to it if you need.
Thanks Patrick! I will probably do that. It's not much that is needed here.

This still leaves open the question of internal runtime structures, such as heap boxes, vecs, and possibly pointers. Unsafe and region pointers seem to be regular machine-word sized values, but I think I read somewhere that some pointers (to traits? something about sized-types?) included an additional word. If somebody can easily point me to some document or specific source code describing this, that would be great. If not, it's OK too, I can always find out by looking into the generated LLVM bitcode :-)

-Michael
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev

Reply via email to