'Sure. My apologies, the vagueness reflects my knowledge level. It's a managerial question to low level programmers about dynamic (external language) programming.
Repharased, I was thinking of types created in external libraries or other environments where the size is unknown to Rust.
Is the best practice to create a trait?
For example the trait in turn could make an unsafe (external to Rust) call to the other environment to query the size of the type. I could pull it (size) out of the data too potentially.
Can I assume all this controversy over the size of ALL types, external in particular, is resolved? I could not find where it was. I can't imagine how it could be.
I need to handle objects both local and passed over networks and from exotic environments (PICK for example.)
My top candidates for crates (ie provisionally. I will add the links today) is:
The static types library:
The persistence library:
And the crates graph page.
A BTree indexing and object database combo (like Mongo)
These are requirements for (yet) another debate application. Web UI.
Someone fixed my OP? Thanks again. I am not entirely sure if this was using group correct terms. Is this post too long?