- 23 Jan, 2015 1 commit
-
-
Matt Bell authored
-
- 13 Jan, 2015 4 commits
-
-
Brian Tiger Chow authored
The pkg.Interface style is modeled after heap.Interface. Generally, I find it helpful for interfaces that have many implementations. It provides clear distinction between the generic interface and the |n| implementations that implement it (which may be interface types themselves). For clients who cannot keep the repo name, one can imagine that the most likely rename is `ipfsrepo`. In that case, `ipfsrepo.Interface` remains meaningful. This is low-pri so it doesn't matter than much. But for the record, the repo.Interface feels appropriate in this use-case.
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
Brian Tiger Chow authored
-
- 06 Jan, 2015 2 commits
- 06 Dec, 2014 1 commit
-
-
Brian Tiger Chow authored
+ style: sort command list License: MIT Signed-off-by: Brian Tiger Chow <brian@perfmode.com>
-
- 18 Nov, 2014 2 commits
-
-
Juan Batiz-Benet authored
-
Matt Bell authored
-
- 14 Nov, 2014 13 commits
-
-
Juan Batiz-Benet authored
Also: - map[cmds.EncodingType]cmds.Marshaller -> MarshalMap cc @mappum @maybebtc
-
Matt Bell authored
-
Matt Bell authored
-
Juan Batiz-Benet authored
The way the current marshallers marshal out output requires a ton of error checking. I wish there was a way to have the library call our marshaller with the right type (rather than an interface). Maybe can do this with Reflect someday.
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Juan Batiz-Benet authored
-
Brian Tiger Chow authored
verified that option text hints match ipfs1 - btc
-
Brian Tiger Chow authored
@mappum, it's okay to make it a read TODO. in fact, it's a really nice practice since it's standard and we can grep it. When someone who has an answer for the concern comes across the standard TODO breadcrumb, he/she can address it. Using the conventional TODO improves discoverability.
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-
Matt Bell authored
-