vindarel

Hello, indeed, and that is a feature. `str:split` explicitly quotes meta characters to not allow regexps. It *should* be explicit with the documentation and the docstring. And indeed, we can...

> if you don't want to add it. I don't close the possibility. > I find it unfortunate however to fall back to ppcre directly to perform a split of...

Thanks for detailing your use case and motivation. > (Insofar I would probably refrain from re-split, but just have a split). `split` with a `:regex` (`:re`? both?) key would be...

Seriously, you don't get style warnings for the two ones that are now set with `setf fdefinition`?

So the issue is that `(str:join " " '(17))` blows up: ``` The value (17) is not of type (OR NULL (CONS STRING T)) when binding STR::STRINGS [Condition of type...

On general, I like this feature. About `substring`: yes, we should not break it. It seems acceptable to create another function with another behavior. We can add `index`, and were...

### substring -> slice \+1 for `slice`. ### insert looks doable. With a warning first, and maybe with a key argument to control the behavior? If someone speaks up we...

I demand code examples ;) First thoughts: - It looks like `:infix` is the current default. - to make the function error on an empty list, I'd give a more...

@tdrhq @charJe Hello, feedback welcome for the naming of these new functions :) `ensure-starts-with`, `ensure-enclosed-by`

Thanks. Indeed, I hesitated with `ensure-prefix`. But I judged that the prefix & suffix related functions are a bit special on their own (for one, they don't accept the usual...