Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiaddr interface feels weird to work with #32

Open
keks opened this issue Sep 12, 2016 · 0 comments
Open

Multiaddr interface feels weird to work with #32

keks opened this issue Sep 12, 2016 · 0 comments

Comments

@keks
Copy link
Contributor

keks commented Sep 12, 2016

On IRC I mentioned that I would expect Push() and Pop() methods, and the idea came up to improve the general UX of the library.

22:34 < keks> is there a reason multiaddr doesn't have push() and pop()? push kind of is 
              Encapsulate, but decapsulate seems to be pop() except that it does the 
              opposite
22:34 < keks> you have to specify the ending and it gives you the beginning. aren't you 
              usually interested in the top of the protocol stack?
22:36 <@jbenet> keks: yeah, the multiaddr util funcs could be expanded.
22:52 <@whyrusleeping> keks: yeah... the multiaddr interface does feel a bit weird
22:53 <@whyrusleeping> should probably open an issue about improving the UX on that
marten-seemann pushed a commit to marten-seemann/go-multiaddr that referenced this issue Feb 25, 2021
…github.com/multiformats/go-multiaddr-net-0.1.1

Bump github.com/multiformats/go-multiaddr-net from 0.0.1 to 0.1.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant