21:03:37pfdietzI have wondered if the scheme-ish approach of compiling with continuations would be useful for a CL compiler where one would want to be able to recompile functions even when they are on the current call stack (for example, if class definitions changed).
21:17:44amerlyqpfdietz: sounds like a good way to splash your brain matters over walls. Execute half of continuation, then recompile, and... continue from the middle of "somewhere"
3:32:41Josh_2Github saying one of my projects is using newlisp xD
3:52:55aethJosh_2: I got that, too, but on Gitlab. They all use the same Ruby package that has a really simple regex and for newlisp it's something like "define-" which is ridiculous because CL has define-condition and lots of custom macros
3:53:30aethJosh_2: The workaround is to add a new .gitattributes file and have this be the one line: *.lisp linguist-language=Common Lisp
3:57:16aethas far as I'm concerned, that's part of the mandatory CL git boilerplate now, along with e.g. a gitignore that ignores all of the FASLs
4:00:31Josh_2magit is awesome, it makes it all so easy
6:43:40eabarbosaor having at files top: ;; -*-lisp-*-