GitLab

This showed up when profile go-ipfs.

This will perform all the correct checks *except* that it won't bother actually
stringifying the multiaddr. It should be significantly faster.

This is checked when the protocol is *registered*. There's no reason to test it
twice.

This is a huge performance hit. Really, we just need to tell users not to modify
the result.

Also, get rid of an unnecessary pointer indirection (no api change).

correctly format ip4-in-6 addresses

fixes part one of #77

Add "ip6%" multiaddr (IPv6 with zone ID)

See [rfc4007].

Can be prefixed to "ip6" like so:

    /zone/eth0/ip6/fe80::1

This corresponds to the rfc4007 address `fe80::1%eth0`

[rfc4007] https://tools.ietf.org/html/rfc4007

docs(README): modify readme

add protocol by code map

Also use `AddProtocol` for *all* protocols (even predefined ones).

fully validate multiaddr byte representations on construction

Otherwise, .String() can panic.

Instead of having the transformers deal with variable length argument prefixes,
just do this in the bytesToString/stringToBytes functions.

begin transition from /ipfs/ to /p2p/ multiaddrs

Two small bugfixes

We were missing a logarithm... CodeToVarint would previously allocate
more bytes than necessary (exponentially) for the varint slice. This bug
was silent but deserves to be fixed nonetheless.

gx: update go-multihash

Add test for Bytes()