Manfred Bergmann

I was actually thinking about adding the discussions link, but thought the source code will probably live longer than the link, or the discussions facility in GitHub. But OK, no...

So it seems `(stream-element-type *standard-output*)` is not setf'able? Getting an error doing this: `Error: Undefined operator (SETF STREAM-ELEMENT-TYPE) in form ((SETF STREAM-ELEMENT-TYPE) #:|Store-Var-1363| #:FORM1364)`. @phoe s variant (tried with both...

No, not at all. Just this one as mentioned by @joaotavora. The strategy it not clear. Do we patch all, or just the ones necessary? Btw: the LW listener in...

Been a while. What's the state @gwbrown ?

Regarding splitting generic vectors. Isn't cl-str specifically a string utility?

> if not, I'd leave a note that explains the reason why str is called str IMO this doesn't need to be explained. Most people probably can figure that the...

> > Isn't cl-str specifically a string utility? > > Yes, right now it is, hence my original proposal from the first post in this thread. Many of the operations...

> I cannot find a good reason why e.g. (join #(a b c) #(1 2 3)) should signal a type error rather than return #(1 a b c 2 a...

I wouldn't care if there are more use-cases beyond string. But it would be good if the current public interface could be maintained and maybe an additional one be added...

> explicitly quotes meta characters to not allow regexps Yeah. I've seen that. Had a glimpse at the sources. > Enhancing the README and the docstring to refer to ppcre...