kiselgra

I could do that, but I often end up having a project-specific meta- or header-file that I want to include in all files. This way I can put it into...

I think this one would be pretty cool and we should be able to do it quite safely on the node-level. The idea would be to allow doc-strings as the...

Hm, I'm not sure. I think it would be nicer to have it more fine-grained. I would like, e.g., to have ```lisp (class foo () "high-level description" ...) ``` generate...

The more familiar (and simpler) notation is definitely a positive, but I also would like to have this transparent to macro-processing. Let's say I have an environment-macro that removes certain...

Cool! Let's do it the easy way first, then see how it works out, if it breaks my current setup :)

I think there has been no work on this until now, but I wanted to note that docstrings for the sake of having documentation in the lisp file really do...

I think this is still an open issue, but wanted to provide the following suggestion. If you use certain templates a lot, the `instantiate`-syntax is a nuisance and it might...

Not sure how /sane/ this is, but we could define another instantiation macro using something similar to split-sequence: (lisp (defun split-seq (seq sym) (loop for x on seq if (not...

That version is still missing a set of parens: ``` inline __attribute__(always_inline) int foo() { return 0; } ``` Adding the pair then generates a function call: ``` inline __attribute__(always_inline)()...

It seems we forgot about a very unfortunate operator: `operator()`. ``` (function operator bool (return true)) (function operator() ((int a) (int b)) -> bool (return true)) (function (comment "operator()" :prefix...