rgkirch
rgkirch
``` #ifndef NO_H_ #define NO_H_ typedef int ELEMENT; #define SODIUM 11; #endif // NO_H_ ``` ``` (Project.config "echo-compiler-cmd" true) (Project.config "echo-c" true) (use IO) (relative-include "no.h") (register-type ELEMENT "ELEMENT" [])...
Running the original example gives me an unhelpful and misleading error message. This is the same source code as https://github.com/carp-lang/Carp/issues/1325 but I didn't have the option to reopen the issue...
This code is bad because I have a `(do (fun 0))` out in space when that's not a valid thing to do in c. I expect it to be not...
why.carp ``` (use Int) (use String) (use IO) (defn say-hi [text] (if (< (length &text) 10) (println "Too short!") (println &text))) ``` macos ``` $ carp why.carp -x Can't call...
`(print #'+)` gives `(print # '+)` https://clojure.org/reference/reader#_dispatch
`#(+ %1 %2)` indented with special-lispy-tab or `i` gives `#(+ % 1 % 2)` which is not the same... `(#(+ %1 %2) 1 2)` gives 3 while `(#(+ % 1...
`"anything here"|{}` `C-d` or `lispy-delete` will delete the braces as well as the preceding string Here are cases that introduce unbalanced braces and brackets: `{}|{}` `[]|[]` `{}|[]` `[]|{}` `[]|()` `{}|()`...
```clojure [[:a] ] ``` If I have the point on the second line after the space and before the close bracket then lispy-backward-kill-word will create ```clojure [[:] ``` another example...
```clojure (def thing [:first :second]) ``` If I mark `:second` with `M-m` (lispy-mark-symbol) and then raise with `r` (special-lispy-raise) then the marked region is messed up. There is no issue...