net/url: API

[rsc]

Receivers are all different names.
Should pick one (probably u).

ParseWithReference should be ParseFragment, both to match
the name of the extra field that it fills in and to avoid confusion
with the other meaning of "reference" used elsewhere in the API.

ParseRequest should be ParseRequestURI to match the URL type's
RequestURI method.

[dsymonds]

Comment 1:

Owner changed to @dsymonds.

Status changed to Started.

[dsymonds]

Comment 2:

Receiver names were regularised in
https://code.google.com/p/go/source/detail?r=1a03fdfef2ab48cc714aa8a74c42dae508b659a1.
ParseWithReference was renamed to ParseWithFragment in
https://code.google.com/p/go/source/detail?r=27d981f51226bc90021c4c3f33f170e4cf04137e.
Open for discussion is what to do with ParseRequest. Russ suggests ParseRequestURI so
match the RequestURI, but the semantics of the two don't exactly match. The function
takes an absolute URI or absolute path; the method is only documented to produce a path
(plus query).

[rsc]

Comment 3:

I think you are falling down the Java rathole, trying to make names
into some kind of standalone essays that need no documentation.
ParseFragment is fine, as is ParseRequestURI.  A RequestURI is exactly
what is being parsed.

[rsc]

Comment 4:

This issue was closed by revision b27bd42.

Status changed to Fixed.