[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31) - #3710

Merged
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix
Apr 8, 2025
Merged

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31)#3710
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix

Conversation

@vincenzopalazzo

@vincenzopalazzovincenzopalazzo commented Apr 5, 2025

Copy link
Copy Markdown
Member

I was using an older version of the compiler, and Clippy did not report any issues. However, after updating to Rust 1.86.0, I was able to reproduce the warnings that we are having inside the CI. This patch proposes an opinionated solution that aligns with Clippy’s suggestions, but I am open to disabling some of the warnings if needed.

The commits include specific changes to highlight the errors, making the review process easier.

Probably @TheBlueMatt will have some opinion on this!

@ldk-reviews-bot

ldk-reviews-bot commented Apr 5, 2025

Copy link
Copy Markdown

👋 Thanks for assigning @valentinewallace as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

```
error: manual implementation of `ok`
--> lightning/src/ln/channel.rs:8551:3
|
8551 | / match self.sign_channel_announcement(node_signer, announcement) {
8552 | | Ok(res) => Some(res),
8553 | | Err(_) => None,
8554 | | }
| |_________^ help: replace with: `self.sign_channel_announcement(node_signer, announcement).ok()`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_ok_err
= note: `-D clippy::manual-ok-err` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_ok_err)]`
```
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
@codecov

codecovBot commented Apr 5, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.04%. Comparing base (c4d23bc) to head (abadb79).

Additional details and impacted files
@@ Coverage Diff @@## main #3710 +/- ##
==========================================
- Coverage 89.04% 89.04% -0.01% 
==========================================
Files 155 155 Lines 122019 122017 -2 Branches 122019 122017 -2 ==========================================
- Hits 108652 108647 -5 - Misses 10701 10710 +9 + Partials 2666 2660 -6 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dunxen

Copy link
Copy Markdown
Contributor

The changes seem minimal and the formatting is being properly corrected, because it's aligning further lines with the leading backtick, unlike before where those instance were aligned with the first letter.

So this LGTM

Comment threadlightning-types/src/features.rs Outdated
Comment threadlightning-types/src/features.rs Outdated

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

@dunxen

Copy link
Copy Markdown
Contributor

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

Yeah, those changes are correct. I think this might have been applied to main (after 3704) here according to suggestions on a CI run (before 3704).

Comment threadci/check-lint.sh Outdated
Comment threadlightning-types/src/features.rs
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@valentinewallacevalentinewallace left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after @dunxen's feedback

@vincenzopalazzo
vincenzopalazzoforce-pushed the macros/docs-fix branch 2 times, most recently from dcbd7f2 to 80a657eCompareApril 7, 2025 20:23
with recent rustc version we can use `repeat_n` instead of `repeat().take()`
```
error: this `repeat().take()` can be written more concisely
--> lightning-invoice/src/ser.rs:256:12
|
256 | Box::new(core::iter::repeat(Fe32::Q).take(to_pad).chain(fes))
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using `repeat_n()` instead: `core::iter::repeat_n(Fe32::Q, to_pad)`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_repeat_n
= note: `-D clippy::manual-repeat-n` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_repeat_n)]`
```
but to keep compatibility with older rustc versions we need to disable the warning
for the `repeat_n` lint.
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
This is the most opinonated suggestion in this sequence of patches.
Probably IDK if would be an option disable this check, but for now
this commit propose a formatting fix to make clippy happy.
```
error: doc list item overindented
--> lightning-types/src/features.rs:62:5
|
62 | //! onion.
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
= note: `-D clippy::doc-overindented-list-items` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::doc_overindented_list_items)]`
error: doc list item overindented
--> lightning-types/src/features.rs:63:5
|
63 | //! (see [BOLT-11](https://github.com/lightning/bolts/blob/master/11-payment-encoding.md) for
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:64:5
|
64 | //! more).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:66:5
|
66 | //! (see
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:67:5
|
67 | //! [BOLT-2](https://github.com/lightning/bolts/blob/master/02-peer-protocol.md#the-channel_ready-message)
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:68:5
|
68 | //! for more info).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: could not compile `lightning-types` (lib) due to 6 previous errors
```
Suggested-by: @dunxen
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, going ahead and landing this as generally trivial and the diff to previous ACKs is minimal.

@tnull
tnull merged commit 06fb142 into lightningdevkit:mainApr 8, 2025
@vincenzopalazzo
vincenzopalazzo deleted the macros/docs-fix branch April 8, 2025 09:26
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@vincenzopalazzo@ldk-reviews-bot@dunxen@tnull@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31) - #3710

Merged
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix
Apr 8, 2025
Merged

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31)#3710
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix

Conversation

@vincenzopalazzo

@vincenzopalazzovincenzopalazzo commented Apr 5, 2025

Copy link
Copy Markdown
Member

I was using an older version of the compiler, and Clippy did not report any issues. However, after updating to Rust 1.86.0, I was able to reproduce the warnings that we are having inside the CI. This patch proposes an opinionated solution that aligns with Clippy’s suggestions, but I am open to disabling some of the warnings if needed.

The commits include specific changes to highlight the errors, making the review process easier.

Probably @TheBlueMatt will have some opinion on this!

@ldk-reviews-bot

ldk-reviews-bot commented Apr 5, 2025

Copy link
Copy Markdown

👋 Thanks for assigning @valentinewallace as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

```
error: manual implementation of `ok`
--> lightning/src/ln/channel.rs:8551:3
|
8551 | / match self.sign_channel_announcement(node_signer, announcement) {
8552 | | Ok(res) => Some(res),
8553 | | Err(_) => None,
8554 | | }
| |_________^ help: replace with: `self.sign_channel_announcement(node_signer, announcement).ok()`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_ok_err
= note: `-D clippy::manual-ok-err` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_ok_err)]`
```
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
@codecov

codecovBot commented Apr 5, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.04%. Comparing base (c4d23bc) to head (abadb79).

Additional details and impacted files
@@ Coverage Diff @@## main #3710 +/- ##
==========================================
- Coverage 89.04% 89.04% -0.01% 
==========================================
Files 155 155 Lines 122019 122017 -2 Branches 122019 122017 -2 ==========================================
- Hits 108652 108647 -5 - Misses 10701 10710 +9 + Partials 2666 2660 -6 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dunxen

Copy link
Copy Markdown
Contributor

The changes seem minimal and the formatting is being properly corrected, because it's aligning further lines with the leading backtick, unlike before where those instance were aligned with the first letter.

So this LGTM

Comment threadlightning-types/src/features.rs Outdated
Comment threadlightning-types/src/features.rs Outdated

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

@dunxen

Copy link
Copy Markdown
Contributor

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

Yeah, those changes are correct. I think this might have been applied to main (after 3704) here according to suggestions on a CI run (before 3704).

Comment threadci/check-lint.sh Outdated
Comment threadlightning-types/src/features.rs
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@valentinewallacevalentinewallace left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after @dunxen's feedback

@vincenzopalazzo
vincenzopalazzoforce-pushed the macros/docs-fix branch 2 times, most recently from dcbd7f2 to 80a657eCompareApril 7, 2025 20:23
with recent rustc version we can use `repeat_n` instead of `repeat().take()`
```
error: this `repeat().take()` can be written more concisely
--> lightning-invoice/src/ser.rs:256:12
|
256 | Box::new(core::iter::repeat(Fe32::Q).take(to_pad).chain(fes))
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using `repeat_n()` instead: `core::iter::repeat_n(Fe32::Q, to_pad)`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_repeat_n
= note: `-D clippy::manual-repeat-n` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_repeat_n)]`
```
but to keep compatibility with older rustc versions we need to disable the warning
for the `repeat_n` lint.
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
This is the most opinonated suggestion in this sequence of patches.
Probably IDK if would be an option disable this check, but for now
this commit propose a formatting fix to make clippy happy.
```
error: doc list item overindented
--> lightning-types/src/features.rs:62:5
|
62 | //! onion.
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
= note: `-D clippy::doc-overindented-list-items` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::doc_overindented_list_items)]`
error: doc list item overindented
--> lightning-types/src/features.rs:63:5
|
63 | //! (see [BOLT-11](https://github.com/lightning/bolts/blob/master/11-payment-encoding.md) for
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:64:5
|
64 | //! more).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:66:5
|
66 | //! (see
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:67:5
|
67 | //! [BOLT-2](https://github.com/lightning/bolts/blob/master/02-peer-protocol.md#the-channel_ready-message)
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:68:5
|
68 | //! for more info).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: could not compile `lightning-types` (lib) due to 6 previous errors
```
Suggested-by: @dunxen
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, going ahead and landing this as generally trivial and the diff to previous ACKs is minimal.

@tnull
tnull merged commit 06fb142 into lightningdevkit:mainApr 8, 2025
@vincenzopalazzo
vincenzopalazzo deleted the macros/docs-fix branch April 8, 2025 09:26
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@vincenzopalazzo@ldk-reviews-bot@dunxen@tnull@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31) - #3710

Merged
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix
Apr 8, 2025
Merged

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31)#3710
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix

Conversation

@vincenzopalazzo

@vincenzopalazzovincenzopalazzo commented Apr 5, 2025

Copy link
Copy Markdown
Member

I was using an older version of the compiler, and Clippy did not report any issues. However, after updating to Rust 1.86.0, I was able to reproduce the warnings that we are having inside the CI. This patch proposes an opinionated solution that aligns with Clippy’s suggestions, but I am open to disabling some of the warnings if needed.

The commits include specific changes to highlight the errors, making the review process easier.

Probably @TheBlueMatt will have some opinion on this!

@ldk-reviews-bot

ldk-reviews-bot commented Apr 5, 2025

Copy link
Copy Markdown

👋 Thanks for assigning @valentinewallace as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

```
error: manual implementation of `ok`
--> lightning/src/ln/channel.rs:8551:3
|
8551 | / match self.sign_channel_announcement(node_signer, announcement) {
8552 | | Ok(res) => Some(res),
8553 | | Err(_) => None,
8554 | | }
| |_________^ help: replace with: `self.sign_channel_announcement(node_signer, announcement).ok()`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_ok_err
= note: `-D clippy::manual-ok-err` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_ok_err)]`
```
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
@codecov

codecovBot commented Apr 5, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.04%. Comparing base (c4d23bc) to head (abadb79).

Additional details and impacted files
@@ Coverage Diff @@## main #3710 +/- ##
==========================================
- Coverage 89.04% 89.04% -0.01% 
==========================================
Files 155 155 Lines 122019 122017 -2 Branches 122019 122017 -2 ==========================================
- Hits 108652 108647 -5 - Misses 10701 10710 +9 + Partials 2666 2660 -6 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dunxen

Copy link
Copy Markdown
Contributor

The changes seem minimal and the formatting is being properly corrected, because it's aligning further lines with the leading backtick, unlike before where those instance were aligned with the first letter.

So this LGTM

Comment threadlightning-types/src/features.rs Outdated
Comment threadlightning-types/src/features.rs Outdated

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

@dunxen

Copy link
Copy Markdown
Contributor

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

Yeah, those changes are correct. I think this might have been applied to main (after 3704) here according to suggestions on a CI run (before 3704).

Comment threadci/check-lint.sh Outdated
Comment threadlightning-types/src/features.rs
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@valentinewallacevalentinewallace left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after @dunxen's feedback

@vincenzopalazzo
vincenzopalazzoforce-pushed the macros/docs-fix branch 2 times, most recently from dcbd7f2 to 80a657eCompareApril 7, 2025 20:23
with recent rustc version we can use `repeat_n` instead of `repeat().take()`
```
error: this `repeat().take()` can be written more concisely
--> lightning-invoice/src/ser.rs:256:12
|
256 | Box::new(core::iter::repeat(Fe32::Q).take(to_pad).chain(fes))
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using `repeat_n()` instead: `core::iter::repeat_n(Fe32::Q, to_pad)`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_repeat_n
= note: `-D clippy::manual-repeat-n` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_repeat_n)]`
```
but to keep compatibility with older rustc versions we need to disable the warning
for the `repeat_n` lint.
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
This is the most opinonated suggestion in this sequence of patches.
Probably IDK if would be an option disable this check, but for now
this commit propose a formatting fix to make clippy happy.
```
error: doc list item overindented
--> lightning-types/src/features.rs:62:5
|
62 | //! onion.
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
= note: `-D clippy::doc-overindented-list-items` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::doc_overindented_list_items)]`
error: doc list item overindented
--> lightning-types/src/features.rs:63:5
|
63 | //! (see [BOLT-11](https://github.com/lightning/bolts/blob/master/11-payment-encoding.md) for
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:64:5
|
64 | //! more).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:66:5
|
66 | //! (see
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:67:5
|
67 | //! [BOLT-2](https://github.com/lightning/bolts/blob/master/02-peer-protocol.md#the-channel_ready-message)
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:68:5
|
68 | //! for more info).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: could not compile `lightning-types` (lib) due to 6 previous errors
```
Suggested-by: @dunxen
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, going ahead and landing this as generally trivial and the diff to previous ACKs is minimal.

@tnull
tnull merged commit 06fb142 into lightningdevkit:mainApr 8, 2025
@vincenzopalazzo
vincenzopalazzo deleted the macros/docs-fix branch April 8, 2025 09:26
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@vincenzopalazzo@ldk-reviews-bot@dunxen@tnull@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31) - #3710

Merged
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix
Apr 8, 2025
Merged

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31)#3710
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix

Conversation

@vincenzopalazzo

@vincenzopalazzovincenzopalazzo commented Apr 5, 2025

Copy link
Copy Markdown
Member

I was using an older version of the compiler, and Clippy did not report any issues. However, after updating to Rust 1.86.0, I was able to reproduce the warnings that we are having inside the CI. This patch proposes an opinionated solution that aligns with Clippy’s suggestions, but I am open to disabling some of the warnings if needed.

The commits include specific changes to highlight the errors, making the review process easier.

Probably @TheBlueMatt will have some opinion on this!

@ldk-reviews-bot

ldk-reviews-bot commented Apr 5, 2025

Copy link
Copy Markdown

👋 Thanks for assigning @valentinewallace as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

```
error: manual implementation of `ok`
--> lightning/src/ln/channel.rs:8551:3
|
8551 | / match self.sign_channel_announcement(node_signer, announcement) {
8552 | | Ok(res) => Some(res),
8553 | | Err(_) => None,
8554 | | }
| |_________^ help: replace with: `self.sign_channel_announcement(node_signer, announcement).ok()`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_ok_err
= note: `-D clippy::manual-ok-err` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_ok_err)]`
```
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
@codecov

codecovBot commented Apr 5, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.04%. Comparing base (c4d23bc) to head (abadb79).

Additional details and impacted files
@@ Coverage Diff @@## main #3710 +/- ##
==========================================
- Coverage 89.04% 89.04% -0.01% 
==========================================
Files 155 155 Lines 122019 122017 -2 Branches 122019 122017 -2 ==========================================
- Hits 108652 108647 -5 - Misses 10701 10710 +9 + Partials 2666 2660 -6 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dunxen

Copy link
Copy Markdown
Contributor

The changes seem minimal and the formatting is being properly corrected, because it's aligning further lines with the leading backtick, unlike before where those instance were aligned with the first letter.

So this LGTM

Comment threadlightning-types/src/features.rs Outdated
Comment threadlightning-types/src/features.rs Outdated

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

@dunxen

Copy link
Copy Markdown
Contributor

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

Yeah, those changes are correct. I think this might have been applied to main (after 3704) here according to suggestions on a CI run (before 3704).

Comment threadci/check-lint.sh Outdated
Comment threadlightning-types/src/features.rs
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@valentinewallacevalentinewallace left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after @dunxen's feedback

@vincenzopalazzo
vincenzopalazzoforce-pushed the macros/docs-fix branch 2 times, most recently from dcbd7f2 to 80a657eCompareApril 7, 2025 20:23
with recent rustc version we can use `repeat_n` instead of `repeat().take()`
```
error: this `repeat().take()` can be written more concisely
--> lightning-invoice/src/ser.rs:256:12
|
256 | Box::new(core::iter::repeat(Fe32::Q).take(to_pad).chain(fes))
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using `repeat_n()` instead: `core::iter::repeat_n(Fe32::Q, to_pad)`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_repeat_n
= note: `-D clippy::manual-repeat-n` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_repeat_n)]`
```
but to keep compatibility with older rustc versions we need to disable the warning
for the `repeat_n` lint.
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
This is the most opinonated suggestion in this sequence of patches.
Probably IDK if would be an option disable this check, but for now
this commit propose a formatting fix to make clippy happy.
```
error: doc list item overindented
--> lightning-types/src/features.rs:62:5
|
62 | //! onion.
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
= note: `-D clippy::doc-overindented-list-items` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::doc_overindented_list_items)]`
error: doc list item overindented
--> lightning-types/src/features.rs:63:5
|
63 | //! (see [BOLT-11](https://github.com/lightning/bolts/blob/master/11-payment-encoding.md) for
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:64:5
|
64 | //! more).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:66:5
|
66 | //! (see
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:67:5
|
67 | //! [BOLT-2](https://github.com/lightning/bolts/blob/master/02-peer-protocol.md#the-channel_ready-message)
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:68:5
|
68 | //! for more info).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: could not compile `lightning-types` (lib) due to 6 previous errors
```
Suggested-by: @dunxen
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, going ahead and landing this as generally trivial and the diff to previous ACKs is minimal.

@tnull
tnull merged commit 06fb142 into lightningdevkit:mainApr 8, 2025
@vincenzopalazzo
vincenzopalazzo deleted the macros/docs-fix branch April 8, 2025 09:26
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@vincenzopalazzo@ldk-reviews-bot@dunxen@tnull@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31) - #3710

Merged
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix
Apr 8, 2025
Merged

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31)#3710
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix

Conversation

@vincenzopalazzo

@vincenzopalazzovincenzopalazzo commented Apr 5, 2025

Copy link
Copy Markdown
Member

I was using an older version of the compiler, and Clippy did not report any issues. However, after updating to Rust 1.86.0, I was able to reproduce the warnings that we are having inside the CI. This patch proposes an opinionated solution that aligns with Clippy’s suggestions, but I am open to disabling some of the warnings if needed.

The commits include specific changes to highlight the errors, making the review process easier.

Probably @TheBlueMatt will have some opinion on this!

@ldk-reviews-bot

ldk-reviews-bot commented Apr 5, 2025

Copy link
Copy Markdown

👋 Thanks for assigning @valentinewallace as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

```
error: manual implementation of `ok`
--> lightning/src/ln/channel.rs:8551:3
|
8551 | / match self.sign_channel_announcement(node_signer, announcement) {
8552 | | Ok(res) => Some(res),
8553 | | Err(_) => None,
8554 | | }
| |_________^ help: replace with: `self.sign_channel_announcement(node_signer, announcement).ok()`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_ok_err
= note: `-D clippy::manual-ok-err` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_ok_err)]`
```
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
@codecov

codecovBot commented Apr 5, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.04%. Comparing base (c4d23bc) to head (abadb79).

Additional details and impacted files
@@ Coverage Diff @@## main #3710 +/- ##
==========================================
- Coverage 89.04% 89.04% -0.01% 
==========================================
Files 155 155 Lines 122019 122017 -2 Branches 122019 122017 -2 ==========================================
- Hits 108652 108647 -5 - Misses 10701 10710 +9 + Partials 2666 2660 -6 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dunxen

Copy link
Copy Markdown
Contributor

The changes seem minimal and the formatting is being properly corrected, because it's aligning further lines with the leading backtick, unlike before where those instance were aligned with the first letter.

So this LGTM

Comment threadlightning-types/src/features.rs Outdated
Comment threadlightning-types/src/features.rs Outdated

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

@dunxen

Copy link
Copy Markdown
Contributor

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

Yeah, those changes are correct. I think this might have been applied to main (after 3704) here according to suggestions on a CI run (before 3704).

Comment threadci/check-lint.sh Outdated
Comment threadlightning-types/src/features.rs
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@valentinewallacevalentinewallace left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after @dunxen's feedback

@vincenzopalazzo
vincenzopalazzoforce-pushed the macros/docs-fix branch 2 times, most recently from dcbd7f2 to 80a657eCompareApril 7, 2025 20:23
with recent rustc version we can use `repeat_n` instead of `repeat().take()`
```
error: this `repeat().take()` can be written more concisely
--> lightning-invoice/src/ser.rs:256:12
|
256 | Box::new(core::iter::repeat(Fe32::Q).take(to_pad).chain(fes))
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using `repeat_n()` instead: `core::iter::repeat_n(Fe32::Q, to_pad)`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_repeat_n
= note: `-D clippy::manual-repeat-n` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_repeat_n)]`
```
but to keep compatibility with older rustc versions we need to disable the warning
for the `repeat_n` lint.
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
This is the most opinonated suggestion in this sequence of patches.
Probably IDK if would be an option disable this check, but for now
this commit propose a formatting fix to make clippy happy.
```
error: doc list item overindented
--> lightning-types/src/features.rs:62:5
|
62 | //! onion.
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
= note: `-D clippy::doc-overindented-list-items` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::doc_overindented_list_items)]`
error: doc list item overindented
--> lightning-types/src/features.rs:63:5
|
63 | //! (see [BOLT-11](https://github.com/lightning/bolts/blob/master/11-payment-encoding.md) for
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:64:5
|
64 | //! more).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:66:5
|
66 | //! (see
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:67:5
|
67 | //! [BOLT-2](https://github.com/lightning/bolts/blob/master/02-peer-protocol.md#the-channel_ready-message)
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:68:5
|
68 | //! for more info).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: could not compile `lightning-types` (lib) due to 6 previous errors
```
Suggested-by: @dunxen
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, going ahead and landing this as generally trivial and the diff to previous ACKs is minimal.

@tnull
tnull merged commit 06fb142 into lightningdevkit:mainApr 8, 2025
@vincenzopalazzo
vincenzopalazzo deleted the macros/docs-fix branch April 8, 2025 09:26
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@vincenzopalazzo@ldk-reviews-bot@dunxen@tnull@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31) - #3710

Merged
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix
Apr 8, 2025
Merged

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31)#3710
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix

Conversation

@vincenzopalazzo

@vincenzopalazzovincenzopalazzo commented Apr 5, 2025

Copy link
Copy Markdown
Member

I was using an older version of the compiler, and Clippy did not report any issues. However, after updating to Rust 1.86.0, I was able to reproduce the warnings that we are having inside the CI. This patch proposes an opinionated solution that aligns with Clippy’s suggestions, but I am open to disabling some of the warnings if needed.

The commits include specific changes to highlight the errors, making the review process easier.

Probably @TheBlueMatt will have some opinion on this!

@ldk-reviews-bot

ldk-reviews-bot commented Apr 5, 2025

Copy link
Copy Markdown

👋 Thanks for assigning @valentinewallace as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

```
error: manual implementation of `ok`
--> lightning/src/ln/channel.rs:8551:3
|
8551 | / match self.sign_channel_announcement(node_signer, announcement) {
8552 | | Ok(res) => Some(res),
8553 | | Err(_) => None,
8554 | | }
| |_________^ help: replace with: `self.sign_channel_announcement(node_signer, announcement).ok()`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_ok_err
= note: `-D clippy::manual-ok-err` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_ok_err)]`
```
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
@codecov

codecovBot commented Apr 5, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.04%. Comparing base (c4d23bc) to head (abadb79).

Additional details and impacted files
@@ Coverage Diff @@## main #3710 +/- ##
==========================================
- Coverage 89.04% 89.04% -0.01% 
==========================================
Files 155 155 Lines 122019 122017 -2 Branches 122019 122017 -2 ==========================================
- Hits 108652 108647 -5 - Misses 10701 10710 +9 + Partials 2666 2660 -6 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dunxen

Copy link
Copy Markdown
Contributor

The changes seem minimal and the formatting is being properly corrected, because it's aligning further lines with the leading backtick, unlike before where those instance were aligned with the first letter.

So this LGTM

Comment threadlightning-types/src/features.rs Outdated
Comment threadlightning-types/src/features.rs Outdated

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

@dunxen

Copy link
Copy Markdown
Contributor

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

Yeah, those changes are correct. I think this might have been applied to main (after 3704) here according to suggestions on a CI run (before 3704).

Comment threadci/check-lint.sh Outdated
Comment threadlightning-types/src/features.rs
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@valentinewallacevalentinewallace left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after @dunxen's feedback

@vincenzopalazzo
vincenzopalazzoforce-pushed the macros/docs-fix branch 2 times, most recently from dcbd7f2 to 80a657eCompareApril 7, 2025 20:23
with recent rustc version we can use `repeat_n` instead of `repeat().take()`
```
error: this `repeat().take()` can be written more concisely
--> lightning-invoice/src/ser.rs:256:12
|
256 | Box::new(core::iter::repeat(Fe32::Q).take(to_pad).chain(fes))
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using `repeat_n()` instead: `core::iter::repeat_n(Fe32::Q, to_pad)`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_repeat_n
= note: `-D clippy::manual-repeat-n` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_repeat_n)]`
```
but to keep compatibility with older rustc versions we need to disable the warning
for the `repeat_n` lint.
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
This is the most opinonated suggestion in this sequence of patches.
Probably IDK if would be an option disable this check, but for now
this commit propose a formatting fix to make clippy happy.
```
error: doc list item overindented
--> lightning-types/src/features.rs:62:5
|
62 | //! onion.
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
= note: `-D clippy::doc-overindented-list-items` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::doc_overindented_list_items)]`
error: doc list item overindented
--> lightning-types/src/features.rs:63:5
|
63 | //! (see [BOLT-11](https://github.com/lightning/bolts/blob/master/11-payment-encoding.md) for
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:64:5
|
64 | //! more).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:66:5
|
66 | //! (see
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:67:5
|
67 | //! [BOLT-2](https://github.com/lightning/bolts/blob/master/02-peer-protocol.md#the-channel_ready-message)
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:68:5
|
68 | //! for more info).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: could not compile `lightning-types` (lib) due to 6 previous errors
```
Suggested-by: @dunxen
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, going ahead and landing this as generally trivial and the diff to previous ACKs is minimal.

@tnull
tnull merged commit 06fb142 into lightningdevkit:mainApr 8, 2025
@vincenzopalazzo
vincenzopalazzo deleted the macros/docs-fix branch April 8, 2025 09:26
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@vincenzopalazzo@ldk-reviews-bot@dunxen@tnull@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31) - #3710

Merged
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix
Apr 8, 2025
Merged

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31)#3710
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix

Conversation

@vincenzopalazzo

@vincenzopalazzovincenzopalazzo commented Apr 5, 2025

Copy link
Copy Markdown
Member

I was using an older version of the compiler, and Clippy did not report any issues. However, after updating to Rust 1.86.0, I was able to reproduce the warnings that we are having inside the CI. This patch proposes an opinionated solution that aligns with Clippy’s suggestions, but I am open to disabling some of the warnings if needed.

The commits include specific changes to highlight the errors, making the review process easier.

Probably @TheBlueMatt will have some opinion on this!

@ldk-reviews-bot

ldk-reviews-bot commented Apr 5, 2025

Copy link
Copy Markdown

👋 Thanks for assigning @valentinewallace as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

```
error: manual implementation of `ok`
--> lightning/src/ln/channel.rs:8551:3
|
8551 | / match self.sign_channel_announcement(node_signer, announcement) {
8552 | | Ok(res) => Some(res),
8553 | | Err(_) => None,
8554 | | }
| |_________^ help: replace with: `self.sign_channel_announcement(node_signer, announcement).ok()`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_ok_err
= note: `-D clippy::manual-ok-err` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_ok_err)]`
```
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
@codecov

codecovBot commented Apr 5, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.04%. Comparing base (c4d23bc) to head (abadb79).

Additional details and impacted files
@@ Coverage Diff @@## main #3710 +/- ##
==========================================
- Coverage 89.04% 89.04% -0.01% 
==========================================
Files 155 155 Lines 122019 122017 -2 Branches 122019 122017 -2 ==========================================
- Hits 108652 108647 -5 - Misses 10701 10710 +9 + Partials 2666 2660 -6 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dunxen

Copy link
Copy Markdown
Contributor

The changes seem minimal and the formatting is being properly corrected, because it's aligning further lines with the leading backtick, unlike before where those instance were aligned with the first letter.

So this LGTM

Comment threadlightning-types/src/features.rs Outdated
Comment threadlightning-types/src/features.rs Outdated

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

@dunxen

Copy link
Copy Markdown
Contributor

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

Yeah, those changes are correct. I think this might have been applied to main (after 3704) here according to suggestions on a CI run (before 3704).

Comment threadci/check-lint.sh Outdated
Comment threadlightning-types/src/features.rs
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@valentinewallacevalentinewallace left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after @dunxen's feedback

@vincenzopalazzo
vincenzopalazzoforce-pushed the macros/docs-fix branch 2 times, most recently from dcbd7f2 to 80a657eCompareApril 7, 2025 20:23
with recent rustc version we can use `repeat_n` instead of `repeat().take()`
```
error: this `repeat().take()` can be written more concisely
--> lightning-invoice/src/ser.rs:256:12
|
256 | Box::new(core::iter::repeat(Fe32::Q).take(to_pad).chain(fes))
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using `repeat_n()` instead: `core::iter::repeat_n(Fe32::Q, to_pad)`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_repeat_n
= note: `-D clippy::manual-repeat-n` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_repeat_n)]`
```
but to keep compatibility with older rustc versions we need to disable the warning
for the `repeat_n` lint.
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
This is the most opinonated suggestion in this sequence of patches.
Probably IDK if would be an option disable this check, but for now
this commit propose a formatting fix to make clippy happy.
```
error: doc list item overindented
--> lightning-types/src/features.rs:62:5
|
62 | //! onion.
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
= note: `-D clippy::doc-overindented-list-items` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::doc_overindented_list_items)]`
error: doc list item overindented
--> lightning-types/src/features.rs:63:5
|
63 | //! (see [BOLT-11](https://github.com/lightning/bolts/blob/master/11-payment-encoding.md) for
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:64:5
|
64 | //! more).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:66:5
|
66 | //! (see
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:67:5
|
67 | //! [BOLT-2](https://github.com/lightning/bolts/blob/master/02-peer-protocol.md#the-channel_ready-message)
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:68:5
|
68 | //! for more info).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: could not compile `lightning-types` (lib) due to 6 previous errors
```
Suggested-by: @dunxen
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, going ahead and landing this as generally trivial and the diff to previous ACKs is minimal.

@tnull
tnull merged commit 06fb142 into lightningdevkit:mainApr 8, 2025
@vincenzopalazzo
vincenzopalazzo deleted the macros/docs-fix branch April 8, 2025 09:26
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@vincenzopalazzo@ldk-reviews-bot@dunxen@tnull@valentinewallace
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31) - #3710

Merged
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix
Apr 8, 2025
Merged

[RFC] clippy new warnings in rustc 1.86.0 (05f9846f8 2025-03-31)#3710
tnull merged 3 commits into
lightningdevkit:mainfrom
vincenzopalazzo:macros/docs-fix

Conversation

@vincenzopalazzo

@vincenzopalazzovincenzopalazzo commented Apr 5, 2025

Copy link
Copy Markdown
Member

I was using an older version of the compiler, and Clippy did not report any issues. However, after updating to Rust 1.86.0, I was able to reproduce the warnings that we are having inside the CI. This patch proposes an opinionated solution that aligns with Clippy’s suggestions, but I am open to disabling some of the warnings if needed.

The commits include specific changes to highlight the errors, making the review process easier.

Probably @TheBlueMatt will have some opinion on this!

@ldk-reviews-bot

ldk-reviews-bot commented Apr 5, 2025

Copy link
Copy Markdown

👋 Thanks for assigning @valentinewallace as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

```
error: manual implementation of `ok`
--> lightning/src/ln/channel.rs:8551:3
|
8551 | / match self.sign_channel_announcement(node_signer, announcement) {
8552 | | Ok(res) => Some(res),
8553 | | Err(_) => None,
8554 | | }
| |_________^ help: replace with: `self.sign_channel_announcement(node_signer, announcement).ok()`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_ok_err
= note: `-D clippy::manual-ok-err` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_ok_err)]`
```
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
@codecov

codecovBot commented Apr 5, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.04%. Comparing base (c4d23bc) to head (abadb79).

Additional details and impacted files
@@ Coverage Diff @@## main #3710 +/- ##
==========================================
- Coverage 89.04% 89.04% -0.01% 
==========================================
Files 155 155 Lines 122019 122017 -2 Branches 122019 122017 -2 ==========================================
- Hits 108652 108647 -5 - Misses 10701 10710 +9 + Partials 2666 2660 -6 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dunxen

Copy link
Copy Markdown
Contributor

The changes seem minimal and the formatting is being properly corrected, because it's aligning further lines with the leading backtick, unlike before where those instance were aligned with the first letter.

So this LGTM

Comment threadlightning-types/src/features.rs Outdated
Comment threadlightning-types/src/features.rs Outdated

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

@dunxen

Copy link
Copy Markdown
Contributor

Hmm, I'm a bit confused why we need to touch features.rs once more, wasn't this solved in #3704 ?

Yeah, those changes are correct. I think this might have been applied to main (after 3704) here according to suggestions on a CI run (before 3704).

Comment threadci/check-lint.sh Outdated
Comment threadlightning-types/src/features.rs
@ldk-reviews-bot

Copy link
Copy Markdown

🔔 1st Reminder

Hey @valentinewallace! This PR has been waiting for your review.
Please take a look when you have a chance. If you're unable to review, please let us know so we can find another reviewer.

@valentinewallacevalentinewallace left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after @dunxen's feedback

@vincenzopalazzo
vincenzopalazzoforce-pushed the macros/docs-fix branch 2 times, most recently from dcbd7f2 to 80a657eCompareApril 7, 2025 20:23
with recent rustc version we can use `repeat_n` instead of `repeat().take()`
```
error: this `repeat().take()` can be written more concisely
--> lightning-invoice/src/ser.rs:256:12
|
256 | Box::new(core::iter::repeat(Fe32::Q).take(to_pad).chain(fes))
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: consider using `repeat_n()` instead: `core::iter::repeat_n(Fe32::Q, to_pad)`
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#manual_repeat_n
= note: `-D clippy::manual-repeat-n` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::manual_repeat_n)]`
```
but to keep compatibility with older rustc versions we need to disable the warning
for the `repeat_n` lint.
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
This is the most opinonated suggestion in this sequence of patches.
Probably IDK if would be an option disable this check, but for now
this commit propose a formatting fix to make clippy happy.
```
error: doc list item overindented
--> lightning-types/src/features.rs:62:5
|
62 | //! onion.
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
= note: `-D clippy::doc-overindented-list-items` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(clippy::doc_overindented_list_items)]`
error: doc list item overindented
--> lightning-types/src/features.rs:63:5
|
63 | //! (see [BOLT-11](https://github.com/lightning/bolts/blob/master/11-payment-encoding.md) for
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:64:5
|
64 | //! more).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:66:5
|
66 | //! (see
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:67:5
|
67 | //! [BOLT-2](https://github.com/lightning/bolts/blob/master/02-peer-protocol.md#the-channel_ready-message)
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: doc list item overindented
--> lightning-types/src/features.rs:68:5
|
68 | //! for more info).
| ^^^ help: try using ` ` (2 spaces)
|
= help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#doc_overindented_list_items
error: could not compile `lightning-types` (lib) due to 6 previous errors
```
Suggested-by: @dunxen
Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>

@tnulltnull left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, going ahead and landing this as generally trivial and the diff to previous ACKs is minimal.

@tnull
tnull merged commit 06fb142 into lightningdevkit:mainApr 8, 2025
@vincenzopalazzo
vincenzopalazzo deleted the macros/docs-fix branch April 8, 2025 09:26
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@vincenzopalazzo@ldk-reviews-bot@dunxen@tnull@valentinewallace