<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-bytes/src/err.rs, branch tor-dirmgr-v0.5.1</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-dirmgr-v0.5.1</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-dirmgr-v0.5.1'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-06-23T12:58:25Z</updated>
<entry>
<title>tor-bytes: Split EncodeError from Error</title>
<updated>2022-06-23T12:58:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-23T12:58:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f699988c411a588b278158bf6852b1a8c63c7454'/>
<id>urn:sha1:f699988c411a588b278158bf6852b1a8c63c7454</id>
<content type='text'>
Since there is currently only one error type that can occur when
encoding, it doesn't make sense to use the full Error type here.

This split will help us downstream, as we no longer need to
categorize tor_bytes::Error as "an error in encoding or decoding".

I considered renaming Error to DecodeError, but that had pretty huge
downstream effects, and didn't seem to be worth it.
</content>
</entry>
<entry>
<title>Style fixes to tor-bytes errors.</title>
<updated>2022-06-22T13:00:59Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-06-22T13:00:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=3120f1092a1984a5904ad4772b9ead9e67905cec'/>
<id>urn:sha1:3120f1092a1984a5904ad4772b9ead9e67905cec</id>
<content type='text'>
Also note an issue with the design of tor-bytes::Error that should
probably go in a separate MR.
</content>
</entry>
<entry>
<title>tor-bytes: Prepare errors for nested reader/writer</title>
<updated>2022-06-09T16:08:56Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-06-07T19:18:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=655804f80414ad68f3a7e1b93ed38bb851e257fc'/>
<id>urn:sha1:655804f80414ad68f3a7e1b93ed38bb851e257fc</id>
<content type='text'>
Writing is going to be able to give errors too.
</content>
</entry>
<entry>
<title>Make Bug from InternalError, add bad_api_usage! and into_bad_api_usage!</title>
<updated>2022-02-15T11:40:24Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-02-14T18:31:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b8f928e4f5cec07c8dff1de9f1c6f09b8dc17efc'/>
<id>urn:sha1:b8f928e4f5cec07c8dff1de9f1c6f09b8dc17efc</id>
<content type='text'>
Including supporting machinery, new kind field, etc.
</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>Move all crates into a `crates` subdirectory.</title>
<updated>2021-08-27T13:53:09Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-08-27T13:53:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=557a0ff40b3731d4690767de27010bbeff08777d'/>
<id>urn:sha1:557a0ff40b3731d4690767de27010bbeff08777d</id>
<content type='text'>
This will cause some pain for now, but now is really the best time
to do this kind of thing.
</content>
</entry>
</feed>
