> What are the downsides of keeping the public fields in a struct which is in turn embedded in a private struct created by the library? That seems similar to u

> What are the downsides of keeping the public fields in a struct which is in turn embedded in a private struct created by the library? That seems similar to using "opaque {}", if I am understanding you correctly? I think either of those solutions could potentially work, at the cost of one explicit cast in each function that actually needs to access the data. I would love to know if this works well enough in practice.