<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dircommon/src, branch arti-v2.5.1</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.1</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v2.5.1'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2026-07-23T10:13:34Z</updated>
<entry>
<title>tor-checkable: TimeRangeBound: Rename extend_tolerance to extend_end_bound</title>
<updated>2026-07-23T10:13:34Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-07-20T14:28:04Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7ce9f5c34c3bdb95e87dac5c8348f6937256c5f5'/>
<id>urn:sha1:7ce9f5c34c3bdb95e87dac5c8348f6937256c5f5</id>
<content type='text'>
It was confusing that one of these functions had "which bound"
mentioned in its name, but the other didn't.  So add `end` and switch
from `tolerance` to `bound` (see previous commit message).

*This* commit should deal only in `extend_tolerance` and `end` and
shouldn't touch `extend_start_bound` or `extend_pre_tolerance`.
</content>
</entry>
<entry>
<title>tor-checkable: TimeRangeBound: Rename extend_pre_tolerance to extend_start_bound</title>
<updated>2026-07-23T10:13:34Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-07-20T10:09:16Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=306fffc11215201aa1b5d6baf84f985bb3fee1bf'/>
<id>urn:sha1:306fffc11215201aa1b5d6baf84f985bb3fee1bf</id>
<content type='text'>
Although it is often used to apply a tolerance, it doesn't make sense
to say that this is extending the "tolerance" of a `TimeRangeBound`.
A `TimeRangeBound` doesn't have a tolerance, only bounds.

Also we should be consistent in our terminology, and use `start`
rather than `pre`.

We'll rename the other method too.  Doing them one at a time will
makes it easier to spot any "pre/start" vs "&lt;nothing&gt;/end" slips:
*this* commit should deal only in `pre` and `start` and shouldn't
touch `extend_tolerance`.
</content>
</entry>
<entry>
<title>Use new TimeRangeBound name throughout the tree</title>
<updated>2026-07-16T15:47:50Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2026-07-16T14:35:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=92c26c4c07be73c91890ed3d7d4e53a06f26d0a1'/>
<id>urn:sha1:92c26c4c07be73c91890ed3d7d4e53a06f26d0a1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>add_warning: add reference to arti#2556</title>
<updated>2026-07-15T17:56:49Z</updated>
<author>
<name>Jim Newsome</name>
<email>jnewsome@torproject.org</email>
</author>
<published>2026-07-15T17:56:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6d333d6e6f0bf4d75fdc81e8865e06f6537d5af6'/>
<id>urn:sha1:6d333d6e6f0bf4d75fdc81e8865e06f6537d5af6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Removed unnecessary lint</title>
<updated>2026-07-15T17:16:51Z</updated>
<author>
<name>pryty26</name>
<email>238962075+pryty26@users.noreply.github.com</email>
</author>
<published>2026-07-15T17:07:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d12e408c1d62f29e58647c91a2714c49e3004cc4'/>
<id>urn:sha1:d12e408c1d62f29e58647c91a2714c49e3004cc4</id>
<content type='text'>
Removed unnecessary lint
</content>
</entry>
<entry>
<title>maint: Run maint/add_warning to deny string slices</title>
<updated>2026-06-09T15:36:01Z</updated>
<author>
<name>Clara Engler</name>
<email>cve@cve.cx</email>
</author>
<published>2026-06-09T15:36:01Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9f5752a77fb57052c06ead0eeae606831f1e8e97'/>
<id>urn:sha1:9f5752a77fb57052c06ead0eeae606831f1e8e97</id>
<content type='text'>
This commit executes maint/add_warning with the just added change to
deny string slices except in tests.

I recommend auditing this by checking out the previous commit followed
by running the script yourself and then verifying that the diff is
identical to this commit.

This commit makes cargo clippy fail.  We will add exceptions in the next
commit.
</content>
</entry>
<entry>
<title>dd(TorConfig): change the order of default vs magic</title>
<updated>2026-05-27T12:05:51Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-05-17T23:49:05Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0fdf73cc2f88256fb6613d9ecc005a4d1f1217f5'/>
<id>urn:sha1:0fdf73cc2f88256fb6613d9ecc005a4d1f1217f5</id>
<content type='text'>
This affects the automatic builder code made by our
derive_deftly macro.  It is only relevant (for now)
in the case of the `NonZero&lt;&gt;` types and their special handling.

Previously, when a builder contained Option&lt;U&gt;,
and we wanted to generate a configuration holding T,
we would _first_ apply a transformation from Option&lt;U&gt; to Option&lt;T&gt;
and _second_ unwrap the result or apply a default.

Now, we _first_ convert from Option&lt;U&gt; to U by applying a default,
and only _then_ perform any necessary conversion from U and T.

This is only relevant in the case where U and T are different.
It simplifies writing the defaults for `NonZero` options,
and will significantly simplify the logic for setting builder defaults.
</content>
</entry>
<entry>
<title>dircommon: Port to use derive_deftly(TorConfig)</title>
<updated>2026-02-17T13:49:49Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2026-02-11T19:32:21Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7fffa9453732decc8b970d94add5529d39472a9d'/>
<id>urn:sha1:7fffa9453732decc8b970d94add5529d39472a9d</id>
<content type='text'>
Some of the behaviors of the existing types here are nonstandard;
I've kept them and documented them, to avoid breaking compatibility.
</content>
</entry>
<entry>
<title>Allow clippy::collapsible_if to trigger</title>
<updated>2026-02-16T15:22:24Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2026-02-09T11:49:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ade1d59e8e44c93b6ee447b72a2948a9652ec44e'/>
<id>urn:sha1:ade1d59e8e44c93b6ee447b72a2948a9652ec44e</id>
<content type='text'>
`clippy::collapsible_if` started triggering after bumping the MSRV to
1.88.

Since this triggers from a lot of places, and since there even are a
couple of instances where we explicitly allow `clippy::collapsible_ifs`,
I've opened #2342 for deciding what to do about it.
</content>
</entry>
<entry>
<title>maint/add_warning: Run script to add new warning</title>
<updated>2026-01-27T18:05:36Z</updated>
<author>
<name>Gabriela Moldovan</name>
<email>gabi@torproject.org</email>
</author>
<published>2026-01-27T18:05:36Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a98faf72eb06b47700faeeac5a8a0dd0fc29b584'/>
<id>urn:sha1:a98faf72eb06b47700faeeac5a8a0dd0fc29b584</id>
<content type='text'>
This adds the lint to all our crates.
</content>
</entry>
</feed>
