freenode/#lisp - IRC Chatlog
Search
6:11:57
dim
I think you might find https://github.com/gwkkwg/cl-containers/blob/master/tests/test-containers.lisp#L142 relevant to your current situation
6:15:35
dim
your main immediate problem is providing an API that handles both push or replace a value for a given dictionnary key, right?
6:18:25
dim
well anyway good luck, my day is done. You seem to always have interesting problems to solve drmeister, have fun!
8:54:20
_death
[] is a terrible name.. there is an association between trying to ape other languages and envy of them
12:05:18
pjb
drmeister: you have 3 solutions: 1- wrap your (cdr (assoc key table :test 'string=)) in a functional abstraction. 2- intern those strings into some package (intern key "PYTHON-SYMBOL"). 3- internalize the strings themselves: (setf (gethash key *interned-strings*) key) with (defparmeter *interned-strings* (make-hash-table :test 'equal) or 'equalp for case insensitivity.
12:05:56
pjb
then (cdr (assoc (intern key "PYTHON-SYMBOLS" table))) or (cdr (assoc (gethash key *interned-strings* table)))
12:07:02
pjb
drmeister: it's rather trivial to write either a macro or a reader macro so that dict["a"] can be interpreted as ([] dict "a").
13:44:47
easye
Anyone know of any open concolic testing CL code <https://en.wikipedia.org/wiki/Concolic_testing>?
13:46:15
easye
err, the language tested doesn't have to be Common Lisp (actually I am interested in many others: JavaScript, EVM, etc.), but is there any concolic testing analysis expressed in CL?
14:31:15
phoe
drmeister: fun trivia, dict["a"] is an M-expression, which was the proposed syntax for Lisp back in the day
14:33:45
pjb
https://www.informatimago.com/develop/lisp/com/informatimago/small-cl-pgms/m-expression/index.html
15:41:09
gendl
Hi, any idea why asdf would suddenly start ignoring asdf/output-translations:*output-translations* ?
15:41:35
gendl
(((#P"/Users/dcooper8/.cache/common-lisp/ccl-1.11-f96-macosx-x64/**/*.*" T) (T T) (T #P"/Users/dcooper8/.cache/common-lisp/ccl-1.11-f96-macosx-x64/**/*.*")))
15:42:39
gendl
same thing with compiling systems etc -- the fasls are just going directly in with the sources
15:43:17
gendl
i'm not sure when this started happening, as far as I know I didn't touch my asdf version... have been running 3.3.1 for a while.
16:17:16
gendl
... working on it... Just started a bare vanilla lisp with asdf, and the output-file is working correctly. So, apparently we're doing something to step on the output-translations at some point. Tracking it down...
16:26:02
gendl
Just cleared all old .fasl files, in ~/.cache/common-lisp, quicklisp/cache/, and the ones which were ending up next to source files, restarted, and now it seems back to normal.
16:26:38
gendl
apparently something was reading one or more stale .fasl files which was causing things to get wedged.
18:03:12
gendl
I finally found the issue. aserve.asd from https://github.com/franzinc/aserve is disabling output-translations.