Thanks! I have two specific questions, if you have a moment.
* Do you have any advice on memory management patterns? It looks like GTSAM code generally uses copies or shared pointers for function arguments, so it seems safe to delete the temporaries, and I make copies (or perhaps RVO heap-allocations) of return values, so those are also safe to delete immediately. Am I seeing all there is to see there? How do python/matlab do it?
* I have the whole thing cross-compiled and running on the new-for-2027 FRC control (a Raspberry Pi 5 compute module on an I/O board). There's a somewhat-standard method of packaging, so that students can install it as a sort of "library" within the WPILib robot-code workflow for deployment and also desktop simulations, etc. The simplest approach to that would be including GTSAM as a git submodule (say, pinned to 4.3a1 at the moment), and running the cmake job as part of the packaging step. There are a few other examples of similar submodule packaging in the wild (e.g. Jan Czarnowski's DeepFactors). Does that seem like a good approach? What do other folks do for packaging?
Thanks again
Joel