You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks to be a semver problem in the deps?
(doesnt occur when building from git)
Compiling harper-ls v0.8.1
error[E0308]: `match` arms have incompatible types
--> /home/jayvdb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/harper-ls-0.8.1/src/tree_sitter_parser.rs:30:24
|
18 | let language = match file_extension {
| ________________________-
19 | | "rs" => tree_sitter_rust::language(),20 | | "tsx" => tree_sitter_typescript::language_tsx(),21 | | "ts" => tree_sitter_typescript::language_typescript(),
... |
29 | | "rb" => tree_sitter_ruby::language(),
| | ---------------------------- this and all prior arms are found to be of type `tree_sitter::Language`
30 | | "swift" => tree_sitter_swift::language(),
| | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `tree_sitter::Language`, found a different `tree_sitter::Language`
... |
34 | | _ => returnNone35 | | };
| |_________- `match` arms have incompatible types
|
= note: `tree_sitter::Language` and `tree_sitter::Language` have similar names, but are actually distinct types
note: `tree_sitter::Language` is defined in crate `tree_sitter`
--> /home/jayvdb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tree-sitter-0.22.1/binding_rust/lib.rs:55:1
|
55 | pub struct Language(*const ffi::TSLanguage);
| ^^^^^^^^^^^^^^^^^^^
note: `tree_sitter::Language` is defined in crate `tree_sitter`
--> /home/jayvdb/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tree-sitter-0.20.10/binding_rust/lib.rs:43:1
|
43 | pub struct Language(*const ffi::TSLanguage);
| ^^^^^^^^^^^^^^^^^^^
= note: perhaps two different versions of crate `tree_sitter` are being used?
The text was updated successfully, but these errors were encountered:
Thank you for bringing this to me attention. I've just pushed a release to crates.io that fixes this issue. Feel free to reopen if this continues to be an issue.
Looks to be a semver problem in the deps?
(doesnt occur when building from git)
The text was updated successfully, but these errors were encountered: