<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti-bench/src/main.rs, branch arti-v1.1.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.1.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-11-04T18:28:40Z</updated>
<entry>
<title>Upgrade to clap 3: replace deprecated functions</title>
<updated>2022-11-04T18:28:40Z</updated>
<author>
<name>Gabriel de Perthuis</name>
<email>g2p.code@gmail.com</email>
</author>
<published>2022-11-04T12:08:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=21a3808684684ef659ba68c6534ae722d7b6b04c'/>
<id>urn:sha1:21a3808684684ef659ba68c6534ae722d7b6b04c</id>
<content type='text'>
Also replace Arg::takes_value with Arg::action to configure flags
that don't take parameters vs options that do.

This makes it easy to upgrade to clap 4.

Tested deprecations with:

    cargo check --workspace --all-features --features clap/deprecated
</content>
</entry>
<entry>
<title>Upgrade to clap 3 with minimal changes</title>
<updated>2022-11-04T18:28:38Z</updated>
<author>
<name>Gabriel de Perthuis</name>
<email>g2p.code@gmail.com</email>
</author>
<published>2022-11-04T09:52:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bc08ea48f7f29c35e73d3dbf0aca23d85877a12f'/>
<id>urn:sha1:bc08ea48f7f29c35e73d3dbf0aca23d85877a12f</id>
<content type='text'>
This removes the last cargo audit override (for the unmaintained
ansi_term).

Don't mark options as required when they have default values:
see &lt;https://github.com/clap-rs/clap/pull/3793&gt;.
</content>
</entry>
<entry>
<title>Run add_warnings.</title>
<updated>2022-11-03T15:06:02Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-03T15:06:02Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=932fe48eaf83f456eefd59475b4486d59966dec3'/>
<id>urn:sha1:932fe48eaf83f456eefd59475b4486d59966dec3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tor-config: Replace dir detection with ConfigurationSource enum</title>
<updated>2022-08-25T14:58:29Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-08-24T17:56:27Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9c00ec7da432a6ecd434fcb5227f50fc349c7162'/>
<id>urn:sha1:9c00ec7da432a6ecd434fcb5227f50fc349c7162</id>
<content type='text'>
As per
  https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/682#note_2830860

And subsequent IRC discussion.

Having done the work as per review comments, I don't much like the
result.  It's quite un-ergonomiuc.  If we can't have fs autodetection,
I think syntactic autodetection within sources.rs would be nearly as
nice.

However, I seem to be outvoted.  At least the externally visible
functionality (of an arti binary, say) is reasonably ergonomic.
</content>
</entry>
<entry>
<title>Run maint/add_warning crates/*/src/{lib,main}.rs</title>
<updated>2022-06-23T18:15:42Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-06-23T18:15:29Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=589c6e52bb49ccfe6c0ad9d18d6b994978e46c6c'/>
<id>urn:sha1:589c6e52bb49ccfe6c0ad9d18d6b994978e46c6c</id>
<content type='text'>
Update all lint blocks
</content>
</entry>
<entry>
<title>lints: Make lint blocks consistent</title>
<updated>2022-05-31T14:24:11Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-31T13:39:09Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fec706c2f3525d38f540e986c94a092fa498734b'/>
<id>urn:sha1:fec706c2f3525d38f540e986c94a092fa498734b</id>
<content type='text'>
The remaining consequences of running add_warning
</content>
</entry>
<entry>
<title>lints: Add let_unit_value allow to all crates</title>
<updated>2022-05-31T14:23:52Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-31T10:46:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4f42101554822c44782c164cac0051e3b4055abd'/>
<id>urn:sha1:4f42101554822c44782c164cac0051e3b4055abd</id>
<content type='text'>
From running add_warning, with manual picking of the right
hunks/lines.
</content>
</entry>
<entry>
<title>lints: Add lint block delimiters to every crate</title>
<updated>2022-05-31T12:00:31Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-30T17:43:12Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=ba0843da4a7ba1e63846a286b870b893092e0a4f'/>
<id>urn:sha1:ba0843da4a7ba1e63846a286b870b893092e0a4f</id>
<content type='text'>
This was the result of:
  maint/add_warning crates/*/src/{lib,main}.rs
and then manually curating the results.
</content>
</entry>
<entry>
<title>Split TorClientConfig out of ArtiConfig, and Resolvable trait</title>
<updated>2022-05-24T19:14:57Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-24T18:07:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=9e526aad7c4ca37e8ee9b082449da6493b6e475b'/>
<id>urn:sha1:9e526aad7c4ca37e8ee9b082449da6493b6e475b</id>
<content type='text'>
This gets rid of `#[serde(flatten)]` which prevents serde_ignored (and
other kinds of introspection) from working properly.

The price is now that the toplevel has to deal with two configuration
objects.

The Resolvable trait is overkill right now, but is going to do More
Things in a moment.  In particular, we need the impl on tuples, so
that the whole config can be processed in one go.
</content>
</entry>
<entry>
<title>fs-mistrust: make Mistrust have a corresponding Builder type.</title>
<updated>2022-05-24T14:54:02Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-18T17:26:01Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=95200383b52d1644d4de357c2a8a50d91fdc1021'/>
<id>urn:sha1:95200383b52d1644d4de357c2a8a50d91fdc1021</id>
<content type='text'>
This is an approximately minimal revision to get Builder in place;
subsequent commits will clean up the API.
</content>
</entry>
</feed>
