2020-07-29
2067
#rust
Thomas Eizinger
22465
Jul 29, 2020 â‹… 7 min read

How to use the Rust compiler as your integration testing framework

Thomas Eizinger I like to think about systems as a whole instead of just dealing with the frontend or backend. Quality matters a lot to me, concerning both the end product and the engineering process that leads to it.

Recent posts:

Getting Started With Claude 4 API: A Developer's Walkthrough

Getting started with Claude 4 API: A developer’s walkthrough

This guide explores how to use Anthropic’s Claude 4 models, including Opus 4 and Sonnet 4, to build AI-powered applications.

Andrew Baisden
Jul 3, 2025 â‹… 16 min read
ai dev tool power rankings

AI dev tool power rankings & comparison [July 2025 edition]

Which AI frontend dev tool reigns supreme in July 2025? Check out our power rankings and use our interactive comparison tool to find out.

Chizaram Ken
Jul 2, 2025 â‹… 3 min read
how API client automation can save you hours in development

How API client automation can save you hours in development

Learn how OpenAPI can automate API client generation to save time, reduce bugs, and streamline how your frontend app talks to backend APIs.

Lewis Cianci
Jul 1, 2025 â‹… 7 min read
Interface Segregation Principle

SOLID series: Understanding the Interface Segregation Principle (ISP)

Discover how the Interface Segregation Principle (ISP) keeps your code lean, modular, and maintainable using real-world analogies and practical examples.

Oyinkansola Awosan
Jun 30, 2025 â‹… 7 min read
View all posts

2 Replies to "How to use the Rust compiler as your integration testing framework"

  1. Hi Thomas, thanks for your article! You write about Percent class, “Because the field within Percent is private, the only to construct an instance of Percent is through the new function.”

    Here is a counterexample:

    #[derive(Debug)]
    struct Percent(f64);

    impl Percent {
    fn new(value: f64) -> anyhow::Result {
    println!(“Creating a Percent object.”);
    if value > 1. {
    anyhow::bail!(“number is too big!”)
    }

    if value < 0. {
    anyhow::bail!("number is too small!")
    }

    Ok(Self(value))
    }
    }

    fn main() {
    let a = Percent::new(0.5);
    let b = Percent(1.6); // this doesn't break, but should!

    println!("Hello, {:?}!", a);
    println!("Hello, {:?}!", b);
    }

  2. Hi Ilya,

    thanks for the comment!
    You are correct that one can still construct an instance of `Percent` if you are within the same module and hence have access to private fields. There is nothing we can do about this but there is also little need to. Generally, it is important that the public API of a module maintains all of the invariants.

    In your case, I would simply put `Percent` into its own module which means all of the “usage” code has to go through the public API and can no longer access the private field. See this playground here: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=0ad00716fe95313d36902679aff41f9e

    Cheers,
    Tom

Leave a Reply