Sam Hughes
Sam Hughes
Maybe we could call it `unsplit`, because `concat` sounds related to `concatMap`, or vice versa. `r.expr(":").unsplit(["foo", "bar"])` => `"foo:bar"`. (And `join` is obviously a bad idea.)
Maybe the separator should be second, but not optional. Or (evil option) the default character should be a zero-width space. But only when r.now() is April 1st.
My serious inclination is to have the separator be second, default value is the empty string. So `.unsplit()` just concatenates strings.
Previously seen in #3863 -- I guess it wasn't fixed as was claimed.
My current theory is that it's a compilation or stdlib bug, or some other platform-specific glitch. I have only briefly looked over the code, but my understanding is: 1. `do_serve`...
@davide1995 No, I haven't been thinking about this at all.
RethinkDB has read-only users. So that could be used to implement this.
I don't get why it was closed. What I mean is, this is generally implementable, by having auth on GUI, or even no-auth but some read-only admin user on GUI,...
Why would we do that?