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
src/racer/matchers.rs:43:23: 43:109 warning: use of deprecated item: use into_iter, #[warn(deprecated)] on by default
src/racer/matchers.rs:43 let it = it.chain(match_fn(src, blobstart, blobend, searchstr, filepath, search_type, local).move_iter());
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The span includes the expression representing the object on which the method is called. That's somewhat annoying, because e.g. vim will place the cursor at the first letter of match_fn in the above example, instead of the first letter of move_iter. It also tends quite confusing, when there's a multi-line expression (e.g. one with a match in it), where the actual method call is a few lines down from where the span begins.
The text was updated successfully, but these errors were encountered:
This updates the `unused` lint group to include more lints, updates the `non_snake_case` lint to give better suggestions, adds a note explaining why a lifetime cannot be elided, and tweaks various error messages. This also updates the `non_uppercase_statics` lint to be warn-by-default to match the other naming lints. For statics, this lint is particularly useful, because a non-uppercase static can easily collide with a pattern binding, resulting in very confusing errors.
Closes#15914.
Closes#15657.
Closes#17337.
ftxqxd
added a commit
to ftxqxd/rust
that referenced
this issue
Oct 3, 2014
The warnings currently look like this:
The span includes the expression representing the object on which the method is called. That's somewhat annoying, because e.g. vim will place the cursor at the first letter of
match_fn
in the above example, instead of the first letter ofmove_iter
. It also tends quite confusing, when there's a multi-line expression (e.g. one with amatch
in it), where the actual method call is a few lines down from where the span begins.The text was updated successfully, but these errors were encountered: