<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-bytes/src/impls.rs, branch arti-v1.1.1</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.1</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.1'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-10-13T13:08:46Z</updated>
<entry>
<title>Fix some rustdoc errors.</title>
<updated>2022-10-13T13:08:46Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-10-13T13:08:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8f267ba1661eb5a5b8ea891ed97289e08a1e8ec4'/>
<id>urn:sha1:8f267ba1661eb5a5b8ea891ed97289e08a1e8ec4</id>
<content type='text'>
In addition to the usual "You named that method wrong!" errors, we
have a new rustdoc error that complains about bogus "HTML tags" that
are actually unquoted usage of types like `Result&lt;Foo&gt;`.
</content>
</entry>
<entry>
<title>tor-bytes::impls: Remove usage of infallible writers.</title>
<updated>2022-07-11T15:18:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-07-09T17:35:57Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9b02cf004cff4fe9f30825d18f2be18b05f2401e'/>
<id>urn:sha1:9b02cf004cff4fe9f30825d18f2be18b05f2401e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Convert each write_onto_infallible implementation into write_onto.</title>
<updated>2022-07-11T15:18:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-07-08T15:37:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=8810af7f6522d43408e30d04d21c4ec6102d73b3'/>
<id>urn:sha1:8810af7f6522d43408e30d04d21c4ec6102d73b3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Convert each write_into_infallible implementation into write_into.</title>
<updated>2022-07-11T15:18:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-07-08T15:37:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e1337bee8fb00a2f5357ddc408828554abaae5e5'/>
<id>urn:sha1:e1337bee8fb00a2f5357ddc408828554abaae5e5</id>
<content type='text'>
(There was only one.)
</content>
</entry>
<entry>
<title>Rename "write" methods on tor-bytes to "write_infallible".</title>
<updated>2022-07-11T15:18:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-07-08T15:20:50Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7938f65c66020d6d7f143307f3336f340f398c63'/>
<id>urn:sha1:7938f65c66020d6d7f143307f3336f340f398c63</id>
<content type='text'>
This comprises four renames:

```
write_onto -&gt; write_onto_infallible
write_into -&gt; write_into_infallible
write -&gt; write_infallible
writer_and_consume -&gt; write_and_consume_infallible.
```

The rest of this branch will be concerned with replacing these
`_infallible` methods with ones that return a `Result`.  This is
part of #513.
</content>
</entry>
<entry>
<title>clippy: Drop an unused lifetime</title>
<updated>2022-05-11T17:51:07Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-11T14:15:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4a06ce01e16ac5a87147c8c80bdf46ffe6a07ce4'/>
<id>urn:sha1:4a06ce01e16ac5a87147c8c80bdf46ffe6a07ce4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Fix grammar and typos</title>
<updated>2022-04-27T12:52:13Z</updated>
<author>
<name>Samanta Navarro</name>
<email>ferivoz@riseup.net</email>
</author>
<published>2022-04-23T11:51:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=c53818d496c910de4dfc4bc8d1f53e419fbf7408'/>
<id>urn:sha1:c53818d496c910de4dfc4bc8d1f53e419fbf7408</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-bytes: Use InternalError.</title>
<updated>2022-02-09T19:39:04Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-02-09T19:39:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7670a26d9c7a5eafa2f0e5cd32785f15a517fc26'/>
<id>urn:sha1:7670a26d9c7a5eafa2f0e5cd32785f15a517fc26</id>
<content type='text'>
This crate's Error type is too low-level to have an ErrorKind, but
it does make sense to use InternalError for the internal errors
here.
</content>
</entry>
<entry>
<title>Upgrade to digest v0.10.0</title>
<updated>2021-12-08T01:33:46Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-08T01:33:46Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4536c2ac873ca7fc490bd65965bbfe41e705cda9'/>
<id>urn:sha1:4536c2ac873ca7fc490bd65965bbfe41e705cda9</id>
<content type='text'>
We generally try to track the latest rust-crypto traits when we can:
fortunately, this upgrade didn't break much, considering.
</content>
</entry>
<entry>
<title>Resolve roughly half of the XXXXs.</title>
<updated>2021-12-06T20:11:03Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-12-06T20:01:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=31b385c5b20205e879a847a9331c30a37dc2e6f5'/>
<id>urn:sha1:31b385c5b20205e879a847a9331c30a37dc2e6f5</id>
<content type='text'>
We want to only use TODO in the codebase for non-blockers, and open
tickets for anything that is a bigger blocker than a TODO.  These
XXXXs seem like definite non-blockers to me.

Part of arti#231.
</content>
</entry>
</feed>
