crates/vm/src/builtins/set.rs (1)

111-113: ⚡ Quick win

Add #[must_use] to PyFrozenSet::elements() for consistency.

The elements() method on PyFrozenSet has the same signature and behavior as PySet::elements() (which now has #[must_use] at line 49), but lacks the attribute. Since both methods allocate a Vec with no side effects, they should both carry the same annotation.

🔧 Suggested fix

+    #[must_use]
     pub fn elements(&self) -> Vec<PyObjectRef> {
         self.inner.elements()
     }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@crates/vm/src/builtins/set.rs` around lines 111 - 113, The
PyFrozenSet::elements() method is missing the #[must_use] attribute like
PySet::elements(); add #[must_use] above the pub fn elements(&self) ->
Vec<PyObjectRef> in the PyFrozenSet impl so callers are warned to use the
returned Vec, mirroring the annotation on PySet::elements().

crates/vm/src/types/slot.rs (1)

40-41: ⚡ Quick win

get_mut is missing a symmetric #[must_use]

get at line 41 now carries #[must_use] but the sibling get_mut at line 50 does not, despite also returning Option<&mut T>. With must_use_candidate enabled as a workspace lint, get_mut will now generate a Clippy warning (and fail CI if warnings are denied).

🔧 Suggested fix

     /// Get a mutable reference to the data if the type matches.
+    #[must_use]
     pub fn get_mut<T: Any + 'static>(&mut self) -> Option<&mut T> {

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@crates/vm/src/types/slot.rs` around lines 40 - 41, The sibling method get_mut
is missing the #[must_use] attribute and will trigger must_use_candidate
warnings; add #[must_use] above the pub fn get_mut<T: Any + 'static>(&mut self)
-> Option<&mut T> declaration so it matches pub fn get<T...>() and avoids Clippy
CI failures, keeping the return type Option<&mut T> unchanged.

crates/vm/src/builtins/asyncgenerator.rs (1)

646-652: 💤 Low value

PyAnextAwaitable::new is missing #[must_use]

PyAnextAwaitable::new is another public constructor in this file that was not annotated while PyAsyncGen::new was. For consistency with the PR's intent:

✏️ Proposed fix

+    #[must_use]
     pub fn new(wrapped: PyObjectRef, default_value: PyObjectRef) -> Self {

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@crates/vm/src/builtins/asyncgenerator.rs` around lines 646 - 652, The
constructor PyAnextAwaitable::new is a public factory that should be annotated
with #[must_use] for consistency and to warn callers when the returned awaitable
is ignored; add the #[must_use] attribute directly above the pub fn new
definition for PyAnextAwaitable (the function named new with signature pub fn
new(wrapped: PyObjectRef, default_value: PyObjectRef) -> Self) so the compiler
will emit a warning if the returned value is not used.

crates/host_env/src/posix.rs (1)

85-87: ⚡ Quick win

Make #[must_use] consistent across all cfg variants of get_number_of_os_threads.

Right now only the fallback implementation is annotated. Adding #[must_use] to the macOS (Line 16) and Linux (Line 63) variants too will keep lint behavior uniform across targets.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@crates/host_env/src/posix.rs` around lines 85 - 87, The three
platform-specific implementations of get_number_of_os_threads have inconsistent
annotation: only the fallback variant has #[must_use]; add #[must_use] above the
macOS and Linux cfg blocks (the functions that implement
get_number_of_os_threads under cfg(target_os = "macos") and cfg(target_os =
"linux")) so all cfg variants have the same must_use lint behavior.

crates/common/src/hash.rs (1)

54-57: ⚡ Quick win

HashSecret::hash_value is missing #[must_use].

hash_bytes, hash_str, and hash_bigint — all returning PyHash — were annotated, but hash_value was not. It would be flagged by must_use_candidate just like the others.

✏️ Proposed fix

+    #[must_use]
     pub fn hash_value<T: Hash + ?Sized>(&self, data: &T) -> PyHash {
         fix_sentinel(mod_int(self.hash_one(data) as _))
     }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@crates/common/src/hash.rs` around lines 54 - 57, The method
HashSecret::hash_value is missing the #[must_use] attribute like the other
hash_* methods; add #[must_use] immediately above the impl method declaration
for hash_value to match hash_bytes, hash_str, and hash_bigint so callers are
warned when the returned PyHash is ignored (target the HashSecret::hash_value
function identifier).

crates/derive-impl/src/lib.rs (1)

77-83: ⚡ Quick win

py_compile and py_freeze are missing #[must_use].

Every other public -> TokenStream function in this file received the annotation, but these two did not. With must_use_candidate now enabled as a workspace lint, Clippy will still warn on them.

✏️ Proposed fix

+#[must_use]
 pub fn py_compile(input: TokenStream, compiler: &dyn Compiler) -> TokenStream {
     result_to_tokens(compile_bytecode::impl_py_compile(input, compiler))
 }

+#[must_use]
 pub fn py_freeze(input: TokenStream, compiler: &dyn Compiler) -> TokenStream {
     result_to_tokens(compile_bytecode::impl_py_freeze(input, compiler))
 }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@crates/derive-impl/src/lib.rs` around lines 77 - 83, Add the #[must_use]
attribute to the public functions that return TokenStream so callers are warned
if the result is ignored; specifically annotate py_compile and py_freeze with
#[must_use] (matching the other public TokenStream-returning functions in this
module) so Clippy's must_use_candidate lint no longer emits warnings for
impl_py_compile/impl_py_freeze wrappers.

crates/vm/src/vm/interpreter.rs (1)

229-256: ⚡ Quick win

init_hook and add_frozen_modules are missing #[must_use].

Both are builder-chain methods returning Self. All other builder methods in this impl block are annotated; these two would still trigger must_use_candidate.

✏️ Proposed fix

+    #[must_use]
     pub fn init_hook<F>(mut self, init: F) -> Self
     where
         F: FnOnce(&mut VirtualMachine) + 'static,
     {
         self.init_hooks.push(Box::new(init));
         self
     }

+    #[must_use]
     pub fn add_frozen_modules<I>(mut self, frozen: I) -> Self
     where
         I: IntoIterator<Item = (&'static str, FrozenModule)>,
     {
         self.frozen_modules.extend(frozen);
         self
     }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@crates/vm/src/vm/interpreter.rs` around lines 229 - 256, The builder methods
init_hook and add_frozen_modules are missing #[must_use]; add the #[must_use]
attribute above both pub fn init_hook<F>(...) -> Self and pub fn
add_frozen_modules<I>(...) -> Self so callers get a compiler warning if the
returned Self is discarded, matching the other builder methods in this impl
block and resolving the must_use_candidate lint.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes