Compilation errors in Debian 9
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- rust
- Domain
- build-system, cli
Research direction
Start by running cargo build with rustc 1.24.1 and inspect the reported locations in src/main.rs: lines 99, 106, and 114-119. Verify the compatibility issue is addressed at those matches, then rerun the build on Debian 9; done means compilation succeeds without these errors.
Written by the indexing model from the issue text.
Description
Ran $ cargo build and rustc (ver 1.24.1) output the following:
Compiling loop-rs v0.4.0 (file:///home/um-li/Downloads/Loop)
error: non-reference pattern used to match a reference (see issue #42640)
--> src/main.rs:99:20
|
99 | if let Some(string) = &opt.until_contains {
| ^^^^^^^^^^^^ help: consider using a reference: `&Some(string)`
error: non-reference pattern used to match a reference (see issue #42640)
--> src/main.rs:106:20
|
106 | if let Some(regex) = &opt.until_match {
| ^^^^^^^^^^^ help: consider using a reference: `&Some(regex)`
error: non-reference pattern used to match a reference (see issue #42640)
--> src/main.rs:114:16
|
114 | if let Some(error_code) = &opt.until_error {
| ^^^^^^^^^^^^^^^^ help: consider using a reference: `&Some(error_code)`
error: non-reference pattern used to match a reference (see issue #42640)
--> src/main.rs:116:17
|
116 | ErrorCode::Any => if !result.exit_status.success() {
| ^^^^^^^^^^^^^^ help: consider using a reference: `&ErrorCode::Any`
error: non-reference pattern used to match a reference (see issue #42640)
--> src/main.rs:119:17
|
119 | ErrorCode::Code(code) => {
| ^^^^^^^^^^^^^^^^^^^^^ help: consider using a reference: `&ErrorCode::Code(code)`
error: aborting due to 5 previous errors
error: Could not compile `loop-rs`.
- Dominant language
- Rust
- Stars
- 697
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Miserlou/Loop
-
Maintainer NeededOpen
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Exponential BackoffOpen
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
-
review-drift
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oxidecomputer/hansei#14 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rubys/roundhouse#444 ·
Maintainers usually reply within 1 day
-
Published hardy-bpa-server image is built without the file-cla featurePossibly taken @EmbryoSpace claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ricktaylor/hardy#755 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
semaphoreci/docker-images#46 · 1 comment ·