Skip to content

rust: self-deref, f()? and expression receivers are not bare calls - #9

Merged
tabladrum merged 1 commit into
mainfrom
release/v0.16.5
Oct 15, 2026
Merged

tabladrum merged 1 commit into
mainfrom
release/v0.16.5

Conversation

@tabladrum

Copy link
Copy Markdown
Contributor

Follow-up to #8: receivers astkit could not name arrived as bare calls; grove's no-rust-analyzer ripgrep recall dropped when bare Rust calls were restricted to free functions. Now self, f()? and <expr>. All 20 grove-eval oracles within baseline, ripgrep without rust-analyzer R .9055 (baseline .9047).

🤖 Generated with Claude Code

https://claude.ai/code/session_01KXa6Cv1ZUXcdMqXcJfQFhX

…calls

`(*self).find(..)`, `(**self).begin(..)`, `args.walk_builder()?.x()` and
`dents[0].path_is_symlink()` arrived as bare calls. They are now `self`,
`walk_builder()?` (the result after `?`) and `<expr>` (a method on an
unnamed value); inside macros a call after `.` is `<expr>` too. grove's
CI (no rust-analyzer) lost 41 true ripgrep edges when bare Rust calls were
restricted to free functions; with this, recall is above baseline.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KXa6Cv1ZUXcdMqXcJfQFhX
@tabladrum
tabladrum merged commit d1fd879 into main Oct 15, 2026
3 checks passed
@tabladrum
tabladrum deleted the release/v0.16.5 branch October 15, 2026 03:03
Sign up for free to 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.

1 participant