"Consuming Interfaces Are Rvalue Reference Qualified" and use-after-move static checks

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

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

    An open-source C++ library developed and used at Facebook.

  • In wg21.link/P1054r0, the paper states that "Consuming Interfaces Are Rvalue Reference Qualified." This seems to make sense to me, both making clear to the reader that the object should not be interacted with after calling e.g. get(), and that tools like bugprone-use-after-move would detect code which attempted to further interact with the Future after it's been consumed. Indeed, Facebook Folly Futures rvalue reference qualify consuming member functions.

  • 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
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