From: Avdi Grimm Date: 2014-07-21T19:45:16-04:00 Subject: [ruby-core:63923] Re: [ruby-trunk - Bug #10075] URI#join needs documentation of its behavior --001a1136a5dc249b0c04febcb479 Content-Type: text/plain; charset=UTF-8 On Mon, Jul 21, 2014 at 10:40 AM, wrote: > Here's my thoughts on this: every other Ruby method I can think of named > `#join` works by concatenating its arguments together with a separator > (possibly with some additional logic to remove redundant separators and > such). > This has caught me by surprise multiple times as well. I don't question the need for a method with these semantics, but the choice of name "join" seems misleading. Too late to change it now, but I wouldn't mind seeing it aliased to a less surprising name (perhaps "#merge_path", per RFC3986) and the "join" version eventually deprecated. --001a1136a5dc249b0c04febcb479 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On M= on, Jul 21, 2014 at 10:40 AM, <jxf+ruby@jxf.me> wrote:
Here's my thoughts on this: every other Ruby method I can think of name= d `#join` works by concatenating its arguments together with a separator (p= ossibly with some additional logic to remove redundant separators and such)= .

This has caught me by surprise multiple ti= mes as well. I don't question the need for a method with these semantic= s, but the choice of name "join" seems misleading. Too late to ch= ange it now, but I wouldn't mind seeing it aliased to a less surprising= name (perhaps "#merge_path", per RFC3986) and the "join&quo= t; version eventually deprecated.=C2=A0
--001a1136a5dc249b0c04febcb479--