16:27:23drmeisteryitzi: It's a very large PR - it's hard to wrap my head around it. Does it compile Cando?
16:29:43yitziYes, it passes the tests also. There is more that I'd like to do, but I am thinking it is best to do it incrementally. I can explain the jist if you want. One of the issues I am concerned with is changing the signature of the startupClasp function to account for exit codes.
16:30:11drmeisteryitzi: Is there a single hook for images and snapshots?
16:30:31drmeisterstartupClasp returns an exit code if there is a problem? That makes sense.
16:33:56nij-If I may continue, here are some more. -- seqan.cc looks for me like a C++ wrapper. In both approach, some wrappers must be written. And whats good about clasp is that the wrapper you need to write is much smaller and more easily to maintain than C wrappers?
16:35:23yitzidrmeister: The options "--noinit, --ignore-image, --base, --image <file>, --snapshot <file>" are all mutually exclusive.
16:36:57yitzidrmeister: To develop cando on the base image (previously called cclasp) you'd just do iclasp -B or iclasp --base .... that would load the base image but continue to load extensions. Boom! solving that probably also.
18:52:07drmeisteryitzi: I've switched to the 'repl' branch and I'm building everything.
18:52:36yitziMake sure you have the repl branch of cando if you are building that.
19:01:17Bikeflipping through git scm on the train. did you know it has a feature to help the "long lived branch that we need to merge main into like eight times" thing we've done a few times? https://git-scm.com/book/en/v2/Git-Tools-Rerere