17:20:12yitziWe have a mess of functions that access global_options like CORE:DEBUGGER-DISABLED. If we use dynamic variables we won't need those to access ClaspInfo.
17:20:24yitziOr remove ones that aren't used. You get the idea.
18:00:23drmeisteryitzi: Question: I'm developing code in the cando/src/lisp/topology/ directory. I want my students to be able to use that code.
18:00:42drmeisterSo I have to push that code and then wait for the overnight build so they can get access to it.
18:01:10drmeisterIt would be faster if I developed it as a quickclasp system wouldn't it?
18:01:50drmeisterI could just update quickclasp and the new code would be available to them with (ql:quickload :foldamer) - or something like that.
18:02:13drmeisterDoes that sound like a faster way to get changes to my students to use them?
18:02:21yitziYes, but if you want it in the eclasp image you'll still need to build.
18:02:59yitziWe could add it to the cando-user-install though, that would add it to the snapshot
18:03:15drmeisterI understand. I can leave slower changing code in cando/src/lisp/xxx and use quickclasp for the more rapid deployment.
18:05:58yitziI think there is kind of three levels: 1) daily in cando repo, 2) add systems to cando-user-install for rebuilding snapshot from quickclasp, 3) use quickload with quickclasp for instantaneous updates.
18:07:16drmeisterOh - I hadn't thought about cando-user-install
18:08:58yitziAdd the system(s) as an dependency to cando-jupyter....that's it
18:10:11yitziYou'll still need to rebuild cando to update the asdf for cando-jupyter, but you put the dependencies into quickclasp until they have stabilized. Then put them into the cando repo.