How to handle read-only Terms about sophia_rs HOT 2 CLOSED

In general, I think that the API should not impose the use of trait objects. Assuming we have a Term trait, having functions accept &T where T: Term is the best option: people who want compile-time optimization can pass references to concrete types; people who want to avoid monomorphization can restrict themselves to passing exclusively dyn references. Everyone can have it their way.

I made one exception to that rule: Graph/Dataset methods return a boxed iterator (hence a trait object), because 1/ it allows for a default implementation, and 2/ the alternative was horribly cumbersome (declaring a bunch of associated types...).

from sophia_rs.

Can we close this, then?

from sophia_rs.