error: non-binding `let` without a type annotation
--> src/fallback.rs:433:9
|
433 | let _ = name;
| ^^^^^^^^^^^^^
|
= help: consider adding a type annotation or removing the `let` keyword
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#let_underscore_untyped
= note: `-D clippy::let-underscore-untyped` implied by `-D clippy::pedantic`
error: non-binding `let` without a type annotation
--> src/fallback.rs:940:21
|
940 | let _ = write!(escaped, "\\x{:02X}", b);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= help: consider adding a type annotation or removing the `let` keyword
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#let_underscore_untyped
error: type parameter goes unused in function definition
--> tests/marker.rs:10:34
|
10 | fn assert_implemented<T: $($marker +)+>() {}
| ^^^^^^^^^^^^^^^^^^
...
42 | assert_impl!(Delimiter is Send and Sync);
| ---------------------------------------- in this macro invocation
|
= help: consider removing the parameter
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_type_parameters
= note: `-D clippy::extra-unused-type-parameters` implied by `-D clippy::all`
= note: this error originates in the macro `assert_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
error: type parameter goes unused in function definition
--> tests/marker.rs:10:34
|
10 | fn assert_implemented<T: $($marker +)+>() {}
| ^^^^^^^^^^^^^^^^^^
...
43 | assert_impl!(Spacing is Send and Sync);
| -------------------------------------- in this macro invocation
|
= help: consider removing the parameter
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_type_parameters
= note: this error originates in the macro `assert_impl` (in Nightly builds, run with -Z macro-backtrace for more info)
error: type parameter goes unused in function definition
--> tests/marker.rs:10:34
|
10 | fn assert_implemented<T: $($marker +)+>() {}
| ^^^^^^^^^^^^^^^^^^
...
80 | / assert_unwind_safe! {
81 | | Delimiter
82 | | Group
83 | | Ident
... |
90 | | TokenTree
91 | | }
| |_____- in this macro invocation
|
= help: consider removing the parameter
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_type_parameters
= note: this error originates in the macro `assert_impl` which comes from the expansion of the macro `assert_unwind_safe` (in Nightly builds, run with -Z macro-backtrace for more info)
I'd like a chance to audit all the code that rustdoc is inserting into
the docs. Currently I am skeptical that showing proc-macro2's internal
usages of APIs is a net benefit to the public documentation. I am also
skeptical that quite so many examples are needed, and that they should
be featured so prominently in comparison to handwritten docs. Lastly I
wish there were a way to turn this behavior off on a more granular
basis.
GitHub's default timeout is 6 hours. Recently some of my GitHub Actions
jobs have started randomly stalling for that long, which is inconvenient
because it ties up a chunk of my runner quota. It apepars to be very
rare for a job to recover after stalling. It's better to time out
quicker and retry on a different runner.
Delete the first paragraph of LICENSE-MIT (an inaccurate
pseudo-copyright line), leaving only the text of the MIT license.
Nothing about the license of proc-macro2 has changed, only our
understanding of how to correctly communicate that license has changed.
This mirrors an equivalent change applied in the rust-lang/rust
repository years ago.
Currently fails with:
thread 'byte_order_mark' panicked at 'called `Result::unwrap()` on
an `Err` value: LexError { span: Span }', tests/test.rs:637:48
