Yuichi Nishiwaki

Since we have `syntax-error` for compile time exception, syntax-assert may be a better name.

No concrete code, only proposal. But the API could be like: ``` string-set!: completely clone the string chunk. transient-string-set!: performed in O(1) time ``` also string->transient and transient->string would be...

@omasanori Though they have the same name, clojure's transient structures and picrin's that are fundamentally different things. transient-string is rather similar to Java's StringBuffer, normal string to String class. And...

Hi guys, the internal representation of picrin's string is now switched to rope! ;) 8586dc9

@KeenS Well, I'm not sure we should or should not take this in to the core. As of now there isn't a package manager and repositories and I agree to...

@omasanori @KeenS Sounds nice. I don't mind changing string internal representation unless it compiles on freestanding environment. UTF-32 sequence is good for programs doing heavy string modifications, but I think...

@omasanori @KeenS Even if it breaks no-libc rule, if we can switch it off with macros, it'll probably be ok.

:+1: I want something like [cffi](http://common-lisp.net/project/cffi/).

Basically, about the way of processing optional arguments, we have two options: 1. provide utility macro(s) 2. extend lambda (and maybe define, too) syntax In the first approach, picrin would...

@stibear let-optional example: ``` (define (foo a b . opts) (let-optionals opts ((c #f) (d 0) (e "")) ...)) ``` If you submit a piece of code of `let-optional` implementation...