<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-rtcompat/src/impls, branch derive-traits</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=derive-traits</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=derive-traits'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-03-02T18:01:18Z</updated>
<entry>
<title>Replace manual Default, and abolish new, in tor-rtcompat</title>
<updated>2022-03-02T18:01:18Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-03-02T17:57:35Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=42f9b3c18670211855e1c4aff86c832c79f0203b'/>
<id>urn:sha1:42f9b3c18670211855e1c4aff86c832c79f0203b</id>
<content type='text'>
The Default impl was the only call site for new()
</content>
</entry>
<entry>
<title>tor-rtcompat: Provide TLS wrapping for all streams</title>
<updated>2022-02-24T14:26:38Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-02-23T17:09:19Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2bbd01b060f4911584e0b151db1cc63cc5bf9715'/>
<id>urn:sha1:2bbd01b060f4911584e0b151db1cc63cc5bf9715</id>
<content type='text'>
Now all of the runtime types we provide all
  impl&lt;S&gt; TlsProvider&lt;S&gt; where S: ...
rather than merely TlsProvider&lt;Self::TcpStream&gt;.

And we document and intent to perhaps require this in the future.
</content>
</entry>
<entry>
<title>tor-rtcompat: remove some unused code.</title>
<updated>2022-01-27T20:52:59Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-27T20:52:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=19f878b3aa7b648605487f94871ab3e5c5b949fd'/>
<id>urn:sha1:19f878b3aa7b648605487f94871ab3e5c5b949fd</id>
<content type='text'>
Nothing actually used these accessor functions, and it's not clear
what would.  We can add them later if they're needed.
</content>
</entry>
<entry>
<title>tor-rtcompat: Add some miscellaneous tests</title>
<updated>2022-01-27T20:48:30Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-27T20:48:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f7373f8b2001d90a63ca08c799e9f47e8f94144d'/>
<id>urn:sha1:f7373f8b2001d90a63ca08c799e9f47e8f94144d</id>
<content type='text'>
These probably aren't for things that will fail IRL, but it's nice
to have coverage on the code, just in case.
</content>
</entry>
<entry>
<title>Rename `SpawnBlocking` trait to `BlockOn`.</title>
<updated>2022-01-26T19:06:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-26T18:59:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bf8fa66d36298561cc868706f748049cec23f5eb'/>
<id>urn:sha1:bf8fa66d36298561cc868706f748049cec23f5eb</id>
<content type='text'>
This avoids a future confusion with the new `SpawnBlocking` trait in
async_executors v0.5, and better describes what the trait provides.
</content>
</entry>
<entry>
<title>Make the native-tls crate optional.</title>
<updated>2022-01-26T19:06:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-26T15:53:06Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=30b3818a9e31b0ebe96d4a32aa9bceb16610f994'/>
<id>urn:sha1:30b3818a9e31b0ebe96d4a32aa9bceb16610f994</id>
<content type='text'>
This commit puts the native-tls crate behind a feature.  The feature
is off-by-default in the tor-rtcompat crate, but can be enabled
either from arti or arti-client.

There is an included script that I used to test that tor-rtcompat
could build and run its tests with all subsets of its features.

Closes #300
</content>
</entry>
<entry>
<title>Limit the inner types in tor-rtcompat that have to implement Clone</title>
<updated>2022-01-26T19:06:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-25T22:22:14Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=05a04220ccc4d0dcbab906db42abc97bad02f222'/>
<id>urn:sha1:05a04220ccc4d0dcbab906db42abc97bad02f222</id>
<content type='text'>
If we implement our own clone on CompoundRuntime, we no longer need
Clone implementations on our TlsProvider implementations.
</content>
</entry>
<entry>
<title>Remove no-longer-needed tokio runtime helper macro</title>
<updated>2022-01-26T19:06:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-25T22:58:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=99c59a8f2b3d1d97110ecdfc1021668f88177c85'/>
<id>urn:sha1:99c59a8f2b3d1d97110ecdfc1021668f88177c85</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Unify TokioRuntime and TokioRuntimeHandle</title>
<updated>2022-01-26T19:06:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-25T21:52:33Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=668364d75d5fec06d235a684dfc6c8c89e543503'/>
<id>urn:sha1:668364d75d5fec06d235a684dfc6c8c89e543503</id>
<content type='text'>
Having separate types here doesn't justify the (very limited)
benefit of distinguishing between the case where we have created an
executor that we own and the case where we have a handle to an
already-running tokio executor.

Part of #301.
</content>
</entry>
<entry>
<title>More comments on the limitations of tor-rtcompat's TLS API</title>
<updated>2022-01-25T18:16:39Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-01-25T18:05:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e4e691a790dc1dfe5b45261a40674a927085c206'/>
<id>urn:sha1:e4e691a790dc1dfe5b45261a40674a927085c206</id>
<content type='text'>
Also, more comments on why these limitations are safe within the
context of Tor, but you wouldn't want to use them elsewhere.
</content>
</entry>
</feed>
