--- title: Changelog #351 | daily.dev description: Rust-analyzer version 0.3.3097 fixes eight bugs. Changes include emitting diagnostics for range patterns with invalid inferred types and fixing a panic in the... canonical: https://daily.dev/posts/changelog-351-ua6qn3cfv twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Changelog #351 | daily.dev og:description: Rust-analyzer version 0.3.3097 fixes eight bugs. Changes include emitting diagnostics for range patterns with invalid inferred types and fixing a panic in the... og:url: https://daily.dev/posts/changelog-351-ua6qn3cfv og:image: https://api.daily.dev/og/posts/uA6qN3cFV.png og:image:alt: Changelog #351 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Changelog #351 **[rust-analyzer](https://daily.dev/sources/rustanalyzer)** · 1 min read · 0 upvotes · 0 comments ## Summary Rust-analyzer version 0.3.3097 fixes eight bugs. Changes include emitting diagnostics for range patterns with invalid inferred types and fixing a panic in the inline_call assist when used with macro calls. Completions now escape keyword module names and offer main and lib modules. Other fixes address ref-match computation on undotted self, NamedTempFile issues on Windows, lockfile lookup through manifest ancestors when fetching Cargo metadata, and status message reporting for clients lacking experimental/serverStatusNotification support. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### why does rust-analyzer panic when I use inline_call on a macro invocation This was a known bug in rust-analyzer where the inline_call assist panicked when used with usages inside macro calls. It was fixed in release 0.3.3097 (commit 0c4d746, dated 2026-10-26), tracked as pull request #23231. _Developers chasing rust-analyzer assist crashes can track fixes like this one on daily.dev._ ### how does rust-analyzer find the Cargo lockfile for metadata resolution Rust-analyzer searches manifest ancestors for the lockfile when fetching Cargo metadata, a behavior fixed in version 0.3.3097. This change addresses cases where the lockfile isn't located directly alongside the manifest being analyzed, improving metadata resolution reliability. _Anyone debugging Cargo workspace metadata quirks can follow rust-analyzer updates on daily.dev._ ## Similar posts on daily.dev - [Changelog \#349](https://daily.dev/posts/changelog-349-abyz1tht0) · rust-analyzer · 0 upvotes · 0 comments - [Changelog \#309](https://daily.dev/posts/changelog-309-boyqc6kza) · rust-analyzer · 0 upvotes · 0 comments - [Changelog \#327](https://daily.dev/posts/changelog-327-gw3ff3jrj) · rust-analyzer · 1 upvotes · 0 comments --- Tags: [#rust](https://daily.dev/tags/rust) [View this post on daily.dev](https://daily.dev/posts/changelog-351-ua6qn3cfv) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Changelog #351","url":"https://daily.dev/posts/changelog-351-ua6qn3cfv","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/changelog-351-ua6qn3cfv"},"datePublished":"2026-10-26T08:37:14.176Z","dateModified":"2026-10-26T08:37:33.511Z","description":"Rust-analyzer version 0.3.3097 fixes eight bugs. Changes include emitting diagnostics for range patterns with invalid inferred types and fixing a panic in the...","image":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","thumbnailUrl":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","isAccessibleForFree":true,"articleSection":"rust-analyzer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"rust-analyzer","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/fb78731d5e4b4a528efc701ed1a634c5","url":"https://daily.dev/sources/rustanalyzer"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/changelog-351-ua6qn3cfv","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"rust","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"rust-analyzer","item":"https://daily.dev/sources/rustanalyzer"},{"@type":"ListItem","position":3,"name":"Changelog #351"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/changelog-351-ua6qn3cfv#faq","mainEntity":[{"@type":"Question","name":"why does rust-analyzer panic when I use inline_call on a macro invocation","acceptedAnswer":{"@type":"Answer","text":"This was a known bug in rust-analyzer where the inline_call assist panicked when used with usages inside macro calls. It was fixed in release 0.3.3097 (commit 0c4d746, dated 2026-10-26), tracked as pull request #23231. Developers chasing rust-analyzer assist crashes can track fixes like this one on daily.dev."}},{"@type":"Question","name":"how does rust-analyzer find the Cargo lockfile for metadata resolution","acceptedAnswer":{"@type":"Answer","text":"Rust-analyzer searches manifest ancestors for the lockfile when fetching Cargo metadata, a behavior fixed in version 0.3.3097. This change addresses cases where the lockfile isn't located directly alongside the manifest being analyzed, improving metadata resolution reliability. Anyone debugging Cargo workspace metadata quirks can follow rust-analyzer updates on daily.dev."}}]} ```