libera/#commonlisp - IRC Chatlog
Search
2:34:46
Jach
Guest92: where I was going with that question was to see if you got a build of sbcl that doesn't have threads enabled, which wouldn't be good.
2:35:01
Jach
But it looks like the only place that calls make-kernel is https://github.com/phantomics/april/blob/63ac3497cad728435e1f0c187e6b19680970ad23/utilities.lisp#L42
2:38:41
Jach
So in the meantime you could in your script just redefine (defun cl-cpus:get-number-of-processors () 2) which should at least let things progress until something else errors
2:48:48
lotuseater
and the quickload generic function can of course also take a list of multiple lib names
3:26:07
moon-child
phantomics: f⍣g⊢y repeatedly applies f to y until y g f y. ⍣≡ is the idiomatic case where g is match, and corresponds to a fixed point
3:34:56
lotuseater
beach: If you want to hear a funny comment about language design, yesterday someone in #clojure stated "Oh it's such a `cool` feature that elisp has implicit progn in the else-branch of IF."
3:38:28
lotuseater
Yes I thought so too. Like the other with "something like pattern matching 100% doesn't belong in a library, it's a built-in feature" like as if the clojure core.match wasn't a lib or such features weren't switched on by a macro
3:41:57
beach
Excellent thank you. I am currently working out the very last steps of SICL bootstrapping. Hope you are fine too.
3:53:32
beach
Working on SICL is a strange experience sometimes, and I don't know whether people creating other Common Lisp implementations have this experience, but most of the SICL code has been executed, which means that it has been somewhat tested. Yet, we still do not create an executable file.
3:58:36
lisp123
beach: Will you be try to create the executable from multiple implementations (SBCL / LispWorks / CCL / CLISP) or just SBCL?
4:00:22
beach
Ultimately, we will test the bootstrapping procedure on several existing Common Lisp implementations, but I don't expect any problems with SICL code itself since it uses only standard Common Lisp plus CLOSER-MOP.
4:01:41
beach
In the past, we exposed a problem with SBCL immobile space (is that what it is called), and we do generate a huge number of funcallable standard objects.
4:02:20
lotuseater
Like don't have the possibility to make executables in LispWorks with the "free" version. ^^
4:03:26
beach
No, the executable I am talking about is a SICL executable file created by writing bytes to disk. What the Common Lisp implementation does not matter.
4:05:06
hayley
"How many layers of metacircularity are you on?" "Like zero dude" "You are like a Python implementation, watch this"
4:05:44
lotuseater
yes when i hear end game that comes to my mind too. yielding the infinity implementation gauntlet to rule the universe
12:41:13
lotuseater
nice :) I had also get used to that LAST returns a list rather than the element alone
12:42:16
hayley
I recall the book Land of Lisp did mention that exact use-case for LAST returning the last cons cell, funnily enough.
12:44:48
Cymew
I might be weird, but I actually think "(setf (car (last list)) 3)" is clearer than last-elt as it forces you to think through the procedure in details. There are a few gotchas in that one.
12:46:09
jackdaniel
you may open code most setf expansions too to better understand low-level operations
13:58:50
didi
If something is EQ+, it has to be EQ too, right? i.e., if (EQL a b), or (EQUAL a b), or (EQUALP a b), it is also true that (EQ a b), isn't it?