How do large projects prevent breaking changes?

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

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

    Run experiments across parts of the Rust ecosystem! (by rust-lang)

  • Automatically run your code against popular open source projects. For example, see Rust's crater or mypy's mypy_primer

  • mypy_primer

    Run mypy and pyright over millions of lines of code

  • Automatically run your code against popular open source projects. For example, see Rust's crater or mypy's mypy_primer

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • Elm

    Compiler for Elm, a functional language for reliable webapps.

  • Statically analyze source code to see if you made any breaking changes. Static analysis can't catch all issues, but can at least detect obvious ones like incompatible type signatures. I know that Elm does this automatically; not sure if this is common in other programming languages.

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