<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/maint/add_warning, branch arti-v1.1.7</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.7</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.7'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2023-07-10T12:49:51Z</updated>
<entry>
<title>clippy: in tests, allow clippy::useless_vec</title>
<updated>2023-07-10T12:49:51Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-10T11:20:22Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=01cb7ee0a1122c435a1c782f08b42fa3bf6969e6'/>
<id>urn:sha1:01cb7ee0a1122c435a1c782f08b42fa3bf6969e6</id>
<content type='text'>
This is a perf issue, only.  If tests are too slow, we will notice and
ca speed them up.  We should optimise for clarity and convenience,
rather than speed.

Forbidding this can result in churn between vec![] and [] as tests are
updated and changed.
</content>
</entry>
<entry>
<title>clippy: globally allow clippy::needless_raw_string_hashes</title>
<updated>2023-07-10T12:49:51Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-07-10T11:15:36Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=43bf89d54024c5d73246eefaea071ab6b3a764eb'/>
<id>urn:sha1:43bf89d54024c5d73246eefaea071ab6b3a764eb</id>
<content type='text'>
Rationale: no-one writes these by default without thinkinh.  If they
are unnecessary, then either the string must have had " in it
before (in which case it might do again), or it is near other strings
which *do* need it.

And having it does no harm; indeed IMO it can increase clarity.

Alternative to !1388's
  Fix new "needless_raw_string_hashes" lint from clippy +nightly
</content>
</entry>
<entry>
<title>add_warning: Tolerate clippy::missing_panics_doc</title>
<updated>2023-07-06T18:29:40Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-07-06T18:29:40Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7e2fa11065b569920cc7ce6ce7ec2ba8ed96389f'/>
<id>urn:sha1:7e2fa11065b569920cc7ce6ce7ec2ba8ed96389f</id>
<content type='text'>
As of current nightly, this lint now includes expect()s,
which makes it trigger way more than we'd like.

See discussion on #950.
</content>
</entry>
<entry>
<title>lints: Promote clippy::print_stderr and clippy::print_stdout</title>
<updated>2023-06-21T11:14:10Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2023-06-21T10:29:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=802200e2382edaaf45a109721c2c5d1e8889d317'/>
<id>urn:sha1:802200e2382edaaf45a109721c2c5d1e8889d317</id>
<content type='text'>
These are available in our MSRV now, so we don't need to handle
specially.  We can just add them to the standard lint block.

(Lint block in every crate will be updated automatically in the next
commit.)
</content>
</entry>
<entry>
<title>Allow clippy::unchecked_duration_subtraction in tests</title>
<updated>2023-01-27T13:28:02Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-27T13:01:45Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a6dd92843edf2bd4c58de62a0d562921e4191ada'/>
<id>urn:sha1:a6dd92843edf2bd4c58de62a0d562921e4191ada</id>
<content type='text'>
This panics on error, and we're fine with a panic on misbehavior in
tests.
</content>
</entry>
<entry>
<title>Disable clippy::unlinlined-format-args</title>
<updated>2023-01-27T13:27:47Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-01-27T12:49:39Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=bf04641c6818cb2c87c6ed9cf463a5710f8919d2'/>
<id>urn:sha1:bf04641c6818cb2c87c6ed9cf463a5710f8919d2</id>
<content type='text'>
This warning kind of snuck up on us! (See #748)  For now, let's
disable it.  (I've cleaned it up in a couple of examples, since
those are meant to be more idiomatic and user-facing.)

Closes #748.
</content>
</entry>
<entry>
<title>shell: use /usr/bin/env instead of absolute paths</title>
<updated>2023-01-25T17:35:53Z</updated>
<author>
<name>Emil Engler</name>
<email>me@emilengler.com</email>
</author>
<published>2023-01-25T17:35:53Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=79097484de7401bf247e14c1bdf5982aee4518a1'/>
<id>urn:sha1:79097484de7401bf247e14c1bdf5982aee4518a1</id>
<content type='text'>
This commit changes the shebang in all shell scripts from absolute
paths (such as `/bin/bash` or `/usr/bin/python3`) to the `/usr/bin/env`
binary with the accompanying interpreter as it's argument.

The reason for this are as follows:
- NixOS cannot work with absolute paths
- BSD systems install their packages in /usr/local/bin
</content>
</entry>
<entry>
<title>add_warnings: ignore clippy::result_large_err</title>
<updated>2022-11-03T15:05:14Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-03T15:05:14Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=e4ca2459dbb9489fe9a4acee32216846a62f4216'/>
<id>urn:sha1:e4ca2459dbb9489fe9a4acee32216846a62f4216</id>
<content type='text'>
This is a temporary workaround for #587 until we get it fixed for
real.
</content>
</entry>
<entry>
<title>add_warnings: work with more non-GNU finds.</title>
<updated>2022-11-03T15:03:43Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-11-03T15:03:43Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0cb886a098797a8674fd93b37125350d17c43677'/>
<id>urn:sha1:0cb886a098797a8674fd93b37125350d17c43677</id>
<content type='text'>
We were doing `find -name '*.rs'`, but `find . -name '*.rs'` (with the .)
is more standard.
</content>
</entry>
<entry>
<title>Allow "clippy::single_char_pattern" in tests.</title>
<updated>2022-10-12T12:50:29Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-10-11T13:00:07Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=82ad9eea5f80331d0e26a7d5ccfeed9e58a615fb'/>
<id>urn:sha1:82ad9eea5f80331d0e26a7d5ccfeed9e58a615fb</id>
<content type='text'>
This lint exists for perf reasons, and this is rarely relevant in
tests.

Using double quoted str is generally cognitively less burdensome.
</content>
</entry>
</feed>
