Email me

Clippy lints / Style

Clippy lint · Style · checked with Clippy 0.1.99

clippy::fn_to_numeric_cast: casting function pointer `fun` to `i64`

What it meansChecks for casts of function pointers to something other than usize. It is in the style group and warns by default.

What you see

warning: casting function pointer `fun` to `i64`
 --> main.rs:4:9
  |
4 | let _ = fun as i64;
  |         ^^^^^^^^^^ help: try: `fun as usize`
  |
  = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#fn_to_numeric_cast
  = note: `#[warn(clippy::fn_to_numeric_cast)]` on by default

Real output of Clippy 0.1.99 (Rust 1.99) on the example below. Names and line numbers in yours will differ.

Does it matter?

Casting a function pointer to anything other than usize/isize is not portable across architectures. If the target type is too small the address would be truncated, and target types larger than usize are unnecessary. Casting to isize also doesn’t make sense, since addresses are never signed.

Code that works but is not idiomatic Rust. Warns by default.

How to fix it

Clippy does not fix this one automatically (its suggestion may change behaviour, so it only shows it). Change the code by hand:

Flagged

fn fun() -> i32 { 1 }
let _ = fun as i64;

Write this instead

let _ = fun as usize;

Turn it off, or on

Allow it where it does not fit your code, as narrowly as you can:

On one item

#[allow(clippy::fn_to_numeric_cast)]
fn my_function() { /* ... */ }

Whole crate (Cargo.toml)

[lints.clippy]
fn_to_numeric_cast = "allow"

One run

cargo clippy -- -A clippy::fn-to-numeric-cast

The [lints] table needs Rust 1.74 or newer. In a workspace, put it under [workspace.lints.clippy] and add [lints] workspace = true to each member.

Stylegroup
warndefault level
nofixed by cargo clippy --fix
pre 1.29.0added in Rust

Clippy's own documentation

What it does

Checks for casts of function pointers to something other than usize.

Why is this bad?

Casting a function pointer to anything other than usize/isize is not portable across architectures. If the target type is too small the address would be truncated, and target types larger than usize are unnecessary.

Casting to isize also doesn’t make sense, since addresses are never signed.

Example

fn fun() -> i32 { 1 }
let _ = fun as i64;

Use instead:

let _ = fun as usize;

From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.

Related lints

All 847 Clippy lints · Rust compiler errors · Cargo.toml checker

Up next

Related lintclippy::needless_returnunneeded `return` statementRead it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ