Michał "phoe" Herda

Is https://lishogi.org/KqG9rkTr the same or a similar bug? The AI did the first move and then spent five minutes doing nothing after my response.

Here is the culprit: https://github.com/madnificent/jsown/blob/744c4407bef58dfa876d9da0b5c0205d869e7977/reader.lisp#L3-L4 Either use `(sb-ext:restrict-compiler-policy 'safety 1)` when compiling `jsown` or switch to a JSON parser which does not commit atrocities like the above. The latter is...

Context: a Clasp MACROEXPAND-ALL implementation is missing in [Swank](https://github.com/slime/slime/blob/2080537746ba808b9c1683a280e803e65f196a9c/swank/clasp.lisp#L336-L339) and [trivial-macroexpand-all](https://github.com/cbaggers/trivial-macroexpand-all/blob/933270ac7107477de1bc92c1fd641fe646a7a8a9/trivial-macroexpand-all.lisp).

Nope, I want the inverse - the official documentation is often out of date and could use efforts that update it, with BT being one example that I am aware...

> On the other hand, `arrow-macros` seems to treat functions and lambdas specially. It would be an extension of the Clojure macro syntax. `(1+ (lambda ...))` does not make sense...

> I'm rather looking forward to either (i) a test suite The [test suite](https://github.com/phoe/binding-arrows/blob/main/t/test.lisp) from `binding-arrows` is free to be adapted as appropriate. The macroexpansion tests will quite obviously need...

Note that as of https://github.com/hipeta/arrow-macros/issues/3#event-4133476273 it seems that arrow-macros no longer implicitly evaluates its arguments.

please fix, this is important

Glad to hear the first part. I'm no good at naming and I'm no a specialist in SB-SIMD so I won't be able to say anything meaningful about naming though.

A naïve non-CL question from a non-SIMD developer: let's assume that we have a structure comprised of a f32 and a ub64, so heterogenous data, 96 bits in total. Is...