Gábor Melis
Gábor Melis
Not sure about conformance, but indenting the list item's body by 4 spaces makes it parse correctly: ``` (let ((3bmd-code-blocks:*code-blocks* t)) (3bmd-grammar:parse-doc " * Added a warning mechanism, which will...
So the problem is that when using the `generic-function` locative instead of e.g. `reader` the docstring is not found. ``` (defclass xxx () ((a :reader xxx-a :documentation "This is XXX-A.")))...
Whoops, I meant to use the `method` locative. ``` (pax:document (pax:locate 'xxx-a '(method () (xxx)))) .. - [method] XXX-A (XXX XXX) .. .. This is XXX-A. .. ``` It seems...
Sounds like a useful feature. As far as I can tell right now, the proposed addition of an `:export-children` argument to `defsection` is the way to go.
I'm aware of the differences between EQ*, but in this case a literal list is compared with, hopefully, itself.
INTERRUPT-THREAD and SCHEDULE-TIMER are unsafe unless it is known that injecting code into an executing thread is okay. In this case, this would require libev to be reentrant among other...
Pushing to *FEATURES\* may not interact well with saved images or executables whose runtime environment can vary.
Very cool. I hope it's enough for quicklisp.
Closing. Feel free to reopen if my reasoning above is incorrect.
Sorry about the latency here. Yes, it will likely break if I move the `quicklisp/` directory, but if the two directories are in the same position relative to each other,...