libera/#sicl - IRC Chatlog
Search
9:40:22
scymtym
this seems like an interesting language environment: https://www.youtube.com/watch?v=72y2EC5fkcE . it is proprietary, unfortunately
9:41:43
paulapatience
No worries, I can make progress on Cleavir with my local checkout of Trucler anyway.
9:50:27
scymtym
beach: yeah. very impressive overall with the incremental native compilation at typing speed, proper debugging and time travel stuff
9:53:37
scymtym
pretty frustrating watching stuff like that while i debug a problem in a unity project that does not happen in the ide, only in the deployed version and every change requires a build which takes 15 minutes
10:14:04
beach
But I think we are on the right path to something much better than we currently have.
16:21:47
paulapatience
I found some omissions and more typos in the manual which I will fix, but probably only after April 1. (I need to concentrate on my research proposal.)
16:38:56
scymtym
i think i am done with the "reader state protocol" for Eclector. this is the new manual section: https://techfak.de/~jmoringe/eclector-manual/eclector.html#Reader-state-protocol . the code changes are here: https://github.com/s-expressionists/Eclector/commit/3a54ad8252d629e593a5a0a391d67d3c7c7e6986
16:39:19
scymtym
if nobody objects, i would like to push this to master and make a release sometime soon™
16:47:32
yitzi
scymtym: So since last time it looks like you just changed the aspect names to the corresponding cl dynamic variable?
16:51:52
yitzi
scymtym: If understand the code, it looks like the readtable aspect is the only one that doesn't default to the corresponding CL dynamic variable?
16:54:14
scymtym
yitzi: correct. package looks different because it has to go (for now) through CALL-WITH-CURRENT-PACKAGE
16:56:02
scymtym
hm, ccl thinks this macro call https://github.com/s-expressionists/Eclector/commit/3a54ad8252d629e593a5a0a391d67d3c7c7e6986#diff-ced2d1a174e6d815baaf8a4fd2846901ea9f662044d6652a8326e758bfa642f2R1287 is not valid for this macro https://github.com/s-expressionists/Eclector/commit/3a54ad8252d629e593a5a0a391d67d3c7c7e6986#diff-e21c245358ad40de3d602a9ace51c36cfaf0611aeb814db532a1e72c8683760aR82
16:56:59
scymtym
the problem seems to be the (&rest bindings &key &allow-other-keys) in the lambda list of the macro
16:58:02
yitzi
scymtym: I've updated the PR so the Clasp tests can run. The build + ansi tests takes about >3 hours on the crappy Github runners. Can't imagine why there would be a failure with Clasp, though. It was just fine with your previous iteration.
17:01:55
scymtym
beach: the link should center the view around a WITH-STATE-VALUES call. but i doesn't matter. i think i know what is going on
17:04:39
scymtym
there is a macro similar to (defmacro with-state-values ((&rest bindings &key &allow-other-keys) …) …) and the macro call is (with-state-values ('*package* …) …). ccl complains "Invalid keyword argument '*PACKAGE* in ('*PACKAGE* …). Valid keyword arguments are NIL."
17:05:45
scymtym
i'm not so sure (except for the "Valid keyword arguments are NIL" part; that's wrong)
17:06:24
scymtym
the keywords and values supplied BINDINGS are evaluated. &key &allow-other-keys was supposed to simply force an even number of arguments
17:07:11
scymtym
ccl is right that the sub-expression '*package* in the macro call is not valid keyword argument (because it is a cons)
17:08:36
scymtym
i guess the simplest solution is to just drop the &key &allow-other-keys and don't make mistakes when calling the macro
17:14:57
scymtym
pjb: actually, i think the problem is that the expression is not a symbol. i wouldn't expect keyword vs. symbol to matter
17:42:14
yitzi
Bike: I think we are blocked from updating the Eclector reader state protocol by the cst:reconstruct changes. Looks like they have been incorporated into Eclector, but not Cleavir yet.
17:43:39
Bike
paulapatience: were you updating cleavir for the cst:reconstruct reordering or should i do that?