rust-multiaddr Should we add an empty MA to the failure test?

Seems that the spec doesn't allow an empty MA.

Human-readable multiaddr: (/<protoName string>/<value string>)+
Example: /ip4/127.0.0.1/udp/1234
Machine-readable multiaddr: (<protoCode uvarint><value []byte>)+
Same example: 0x4 0x7f 0x0 0x0 0x1 0x91 0x2 0x4 0xd2
Values are usually length-prefixed with a uvarint

Mar 22 '23 13:03 diegomrsantos

Where in the provided snippet do you read that an empty address is not allowed?

Mar 22 '23 14:03 thomaseizinger

Doesn't "+" mean 1 or more?

Mar 22 '23 15:03 diegomrsantos

Also see https://github.com/multiformats/go-multiaddr/issues/104

Mar 22 '23 16:03 Menduist

Doesn't "+" mean 1 or more?

Ah yes, I didn't realize that was actually a regular expression.

Mar 22 '23 21:03 thomaseizinger

We could deprecate the Multiaddr::empty function and replace it with a Multiaddr::new(Protocol) one.

Mar 22 '23 21:03 thomaseizinger