<p dir="auto">Should we add PathEscape and PathUnescape functions, similar to QueryEscape and QueryUnescape? The functionality is already present (see func (*URL) EscapedPath), but it is awkward to use.</p>
<p dir="auto">See <a href="https://groups.google.com/forum/#!topic/golang-dev/UDUqvuKrq14" rel="nofollow">https://groups.google.com/forum/#!topic/golang-dev/UDUqvuKrq14</a> for golang-dev discussion</p>
<pre class="notranslate">Compile this file (loosely based on test/named1.go) with 6g:

package p

type Bool bool
type Int int
type String string

func B(Bool) {}
func I(Int) {}
func S(String) {}

func F() {
    B(1 == 2)
    I(1 + 2)
    S("1" + "2")
}

I see this:

foo.go:12: cannot use false (type ideal bool) as type Bool in function argument

If the type of "1 == 2" is in fact "ideal bool", then it would seem
that the function call should be permitted, by analogy with the other two function
calls.  However, the spec currently says "Comparison operators compare two operands
and yield a value of type bool".  From that I conclude that the compiler is correct
to give an error, but that the error message should say "type bool", not
"type ideal bool".</pre>