Module solmate_safe_transfer_lib 

Re-exports

use super::SolmateSafeTransferLib; 🔒

use crate::linter::LateLintPass; 🔒

use crate::linter::LintContext; 🔒

use crate::sol::Severity; 🔒

use crate::sol::SolLint; 🔒

use crate::sol::analysis::source_in_package; 🔒

use solar::sema::Gcx; 🔒

use solar::sema::hir::Expr; 🔒

use solar::sema::hir::ExprKind; 🔒

use solar::sema::hir::FunctionId; 🔒

Statics

SOLMATE_SAFE_TRANSFER_LIB

Functions

is_unchecked_token_op 🔒

Whether function_id is one of the token operations of solmate’s SafeTransferLib. safeTransferETH stays out: sending ETH involves no token code. A same-name function of another library (Uniswap’s TransferHelper style) stays out through the resolution, and so does a same-name library from another package (Solady’s SafeTransferLib checks token code on the empty-return path), which fails the provenance check: the declaring source must come from a solmate package path (lib/solmate, solmate/...). Matching a whole path component rather than a substring keeps a vendored or patched copy under a misleading path such as vendor/solmate-fixed/ from being recognized.