Electron100
commented
1 year ago I like the goal, but I'm not wild about the clones (or of the fact that it's a breaking change by requiring the type be clonable), or of the fact that it tries to save again unconditionally even when it may not be necessary. I posted #116 for comparative discussion. It's much less ambitious in that it doesn't achieve the full goal of saving automatically, but it at least makes it harder to accidentally shoot oneself in the foot.
If we want to do automatic save, I'd lean more towards doing that save right away in the add method rather than cloning to do it later in the save. Of course that would require adding the connection as a parameter, which would be a breaking change too.
As a side tangent, while I like a lot of the decisions in Rust, the biggest thing I miss compared to the languages I use in my day job (primarily Kotlin with smatterings of Java, C++, and C#) is method overloading. I slightly-grudgingly understand the reasoning for not supporting type-based overloading, but I do wish we could at least have overloading on arity.
jayvdb
Attempt at solving https://github.com/Electron100/butane/issues/109 It still has lots of todo's:
Manyreferences. I'm not sure if butane can support this at the moment. (There is self-referential fkey support) If so, this auto-save feature will need to be feature flagged.