- 17 Jan, 2016 1 commit
-
-
Jeromy authored
-
- 25 Sep, 2015 1 commit
-
-
David Stainton authored
-
- 31 Aug, 2015 1 commit
-
-
David Stainton authored
-
- 29 Aug, 2015 2 commits
-
-
Leif Ryge authored
-
David Stainton authored
-
- 18 Jan, 2015 1 commit
-
-
Juan Batiz-Benet authored
-
- 09 Jan, 2015 3 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 19 Nov, 2014 1 commit
-
-
Juan Batiz-Benet authored
-
- 05 Nov, 2014 2 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
- 11 Oct, 2014 1 commit
-
-
Juan Batiz-Benet authored
-
- 06 Oct, 2014 2 commits
-
-
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
-
Juan Batiz-Benet authored
The error in String should not actually ocurr, as the multiaddr should have been valid to be constructed successfully, and thus should be encoded back to its string rep correctly. This will be bolstered by creating an interface (to prevent messing with the internal bytes)
-
- 16 Sep, 2014 1 commit
-
-
Juan Batiz-Benet authored
-
- 11 Sep, 2014 1 commit
-
-
Juan Batiz-Benet authored
-
- 07 Jul, 2014 1 commit
-
-
Juan Batiz-Benet authored
-
- 04 Jul, 2014 4 commits
-
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-