- 21 Sep, 2017 2 commits
-
-
Steven Allen authored
no point in slowing things down unnecessarily just for some debugging code.
-
Steven Allen authored
This was showing up on CPU profiles as a significant source of repeated allocations. We don't really care about over allocation (don't keep these slices around) and should rarely have more than 8 protocols in a single address.
-
- 19 Sep, 2016 1 commit
-
-
jbenet authored
-
- 04 May, 2016 1 commit
-
-
Jeromy authored
-
- 29 Apr, 2016 1 commit
-
-
Jeromy authored
-
- 18 Jan, 2016 1 commit
-
-
Jeromy authored
-
- 17 Jan, 2016 1 commit
-
-
Jeromy authored
-
- 20 Jan, 2015 1 commit
-
-
Juan Batiz-Benet authored
-
- 09 Jan, 2015 1 commit
-
-
Juan Batiz-Benet authored
-
- 19 Nov, 2014 1 commit
-
-
Juan Batiz-Benet authored
-
- 05 Nov, 2014 4 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 06 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
This commit changes the struct to a new Multiaddr interface: ```Go type Multiaddr interface { Equal(Multiaddr) bool Bytes() []byte String() string Protocols() []*Protocol Encapsulate(Multiaddr) Multiaddr Decapsulate(Multiaddr) Multiaddr } ``` This means a few things have changed: - use Multiaddr interface, struct not exported - Bytes returns a copy of the internal bytes - Some methods no longer return errors (catch errors in NewMultiaddr) - String (panics if malformed) - Protocols (panics if malformed) - Decapsulate (no-op if not prefix) - Moved net-specific functions to package - Multiaddr.DialArgs() -> DialArgs(Multiaddr) - Multiaddr.IsThinWaist() -> IsThinWaist(Multiaddr) cc @whyrusleeping @perfmode
-