<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-linkspec/src, branch arti-v1.3.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.3.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-10-22T20:46:58Z</updated>
<entry>
<title>linkspec: Fix nightly warning about elided lifetime</title>
<updated>2024-10-22T20:46:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-10-22T20:46:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9668b0b913e3b37deb7eda9e1beb292d33c08cf1'/>
<id>urn:sha1:9668b0b913e3b37deb7eda9e1beb292d33c08cf1</id>
<content type='text'>
This warning shows up when running `cargo +nightly doc`.
Apparently nightly doesn't like it when we have elided a lifetime
that has a perfectly good name.
</content>
</entry>
<entry>
<title>Some HasMemoryCost impls in tor-linkspec</title>
<updated>2024-10-02T18:11:26Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-26T20:18:43Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=213fef3fbc73f45064e0ff9ec0c6737cf7a4ccdd'/>
<id>urn:sha1:213fef3fbc73f45064e0ff9ec0c6737cf7a4ccdd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-chanmgr: don't allow pending channels with no relay ids</title>
<updated>2024-10-02T01:20:07Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2024-10-01T01:45:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d1156da2bd69472cac7883a3643020a700b005d2'/>
<id>urn:sha1:d1156da2bd69472cac7883a3643020a700b005d2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'orport' into 'main'</title>
<updated>2024-09-30T20:19:29Z</updated>
<author>
<name>opara</name>
<email>opara@torproject.org</email>
</author>
<published>2024-09-30T20:19:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bcd1aafd102b9c7ec9c8e231f2b5f93acf5e7ce3'/>
<id>urn:sha1:bcd1aafd102b9c7ec9c8e231f2b5f93acf5e7ce3</id>
<content type='text'>
tor-chanmgr: support multiple channels for a relay ID

See merge request tpo/core/arti!2442</content>
</entry>
<entry>
<title>Upgrade to derive_more version 1.0.0</title>
<updated>2024-09-25T14:37:18Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2024-09-25T14:37:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6a12c2ba8515226a772d5f4a81930bf42d67535a'/>
<id>urn:sha1:6a12c2ba8515226a772d5f4a81930bf42d67535a</id>
<content type='text'>
The `derive_more` crate broke backward compatibility with this version,
so this change involved quite a few manual fixups.
With luck, they'll keep compatibility for some while in the future.
</content>
</entry>
<entry>
<title>tor-linkspec: add `ListByRelayIds`</title>
<updated>2024-09-24T00:50:19Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2024-09-23T16:15:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cb69e46717ee552f29eabb2e91c20d9d6cd517e1'/>
<id>urn:sha1:cb69e46717ee552f29eabb2e91c20d9d6cd517e1</id>
<content type='text'>
Like `ByRelayIds`, but allows multiple items per relay ID.
</content>
</entry>
<entry>
<title>tor-linkspec: impl `HasAddrs` for `&amp;T`</title>
<updated>2024-09-24T00:50:19Z</updated>
<author>
<name>Steven Engler</name>
<email>opara@torproject.org</email>
</author>
<published>2024-09-23T16:11:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=573f1dcf7609789d7fc4341f5c5d901866573a27'/>
<id>urn:sha1:573f1dcf7609789d7fc4341f5c5d901866573a27</id>
<content type='text'>
This makes the `HasAddrs` trait nicer to use when most things that have
addresses are passed by reference anyways.
</content>
</entry>
<entry>
<title>tor_bytes: Rename new_truncated_for_test to new_incomplete_for_test (fmt)</title>
<updated>2024-09-12T11:48:39Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-11T15:52:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8c2c1170daa9b1fc4a13177edd3881e934b99899'/>
<id>urn:sha1:8c2c1170daa9b1fc4a13177edd3881e934b99899</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor_bytes: Rename new_truncated_for_test to new_incomplete_for_test</title>
<updated>2024-09-12T11:48:38Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-11T15:51:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5314741adecad01014a069c4f0ed5018e0f6c207'/>
<id>urn:sha1:5314741adecad01014a069c4f0ed5018e0f6c207</id>
<content type='text'>
No semver implications since this wasn't in the last release.
</content>
</entry>
<entry>
<title>tor-bytes: Add a Reader constructor for use in tests</title>
<updated>2024-09-11T13:19:19Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-09-11T12:04:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=98e563764b428e4f1aa87dc34e5fa6b5cf296938'/>
<id>urn:sha1:98e563764b428e4f1aa87dc34e5fa6b5cf296938</id>
<content type='text'>
We could call from_possibly_incomplete_slice in these, but that's
confusing and distracting.

Here we add this constructor, and document it (in terms of the
constructor to come), and change the call sites.

No functional change.  Doing this now will prevent unwanted changes to
test behaviours when we change the behaviour of Readers made by
Reader::from_slice.
</content>
</entry>
</feed>
