Is implicit typing in Rust always guaranteed to have the same behavior?

This page summarizes the projects mentioned and recommended in the original post on /r/rust

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • rfcs

    RFCs for changes to Rust

  • As other said, only implicit typing in Rust is for integer and float see RFC 212. I don't like at all this exception in Rust, I don't like exception if they are avoidable, specially the rational in the RFC say "first encounter with Rust", so the purpose is to make it more simple for Rust beginner to "start" with Rust.

  • rust

    Empowering everyone to build reliable and efficient software.

  • This changed (as I warm of it 8 years ago...) because a pointer isn't just a number, pointer is "something that contains information for a system about memory location", Rust didn't care about this problem until people from Rust wanted to use Rust on CHERI and discover that well CHERI have provenance information in pointer and you can't use processor bus size to store a pointer. So now usize is address size integer. More info https://github.com/rust-lang/rust/issues/95228

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • validator

    Simple validation for Rust structs (by Keats)

  • (That's how certain kinds of extensibility work in the validator crate. You just impl a method and validator won't care where it comes from as long as it's in scope because it's built using declarative macros.)

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts