Search
Wednesday, 23rd of November 2022, 12:46:46 UTC
12:52:41
ak-coram`
compiling ironclad takes quite some time, it's a shame uuid relies on the whole thing when it really only needs two digest functions (md5 / sha1)
12:53:52
jackdaniel
I think that there was a separate uuid library that did not rely on ironclad
12:53:55
jackdaniel
but I may remember wrong
12:54:21
ak-coram`
jackdaniel: there's a workaround in it for clasp which provides these digests
13:04:01
ak-coram`
jackdaniel: maybe this one? https://github.com/deterministic-arts/DartsCLUUID
13:04:30
ak-coram`
seems this is ironclad too
13:04:40
jackdaniel
I might have remembered wrong
13:05:03
ak-coram`
there's also something called random-uuid in ql, but I can't find it anywhere else
13:05:25
ak-coram`
https://git.mfiano.net/mfiano/random-uuid
13:05:35
ak-coram`
looks like this one is gone
15:14:27
splittist
ak-coram`: do you need a 'real' UUID? Or would (random (1- (expt 2 128))) (or whatever) work?
17:25:45
ak-coram`
splittist: currently I use it to represent the database UUID type in cl-duckdb
17:26:43
ak-coram`
might as well switch to strings, but since I get the UUID in binary form, it seemed nice and efficient to directly create these
17:27:10
ak-coram`
https://github.com/ak-coram/cl-duckdb/blob/main/duckdb-api.lisp#L77
17:30:54
ak-coram`
but I guess it depends on what people use this for
17:31:15
ak-coram`
if you're already using the uuid package, this works great
17:31:51
ak-coram`
I'm also just a bit annoyed by my 30m ECL CI runs...
17:46:07
jackdaniel
most of the compilation time is spend in gcc, so it is not something I can easily address :C
23:20:42
ak-coram`
jackdaniel: no blame there :)
23:20:58
ak-coram`
also I have no issues with ironclad
23:21:10
ak-coram`
just maybe uuid could be done without it
23:21:41
ak-coram`
as evidenced by clasp
Thursday, 24th of November 2022, 0:46:46 UTC