Skip to content

Migrate code base to C++26 #1257

@soroshsabz

Description

@soroshsabz

ITNOA

I think C++20 and C++26 introduces many useful features.

some useful features are

  • Modules (for better performance and library exposure)
  • Concepts (for better meta programming)
  • Contracts (for robust coding)
  • std::optionals (for more declarative options)
  • std::variants (same as above)
  • std::any (same as above)
  • structured binding (for better API)
  • std::span (for better performance)
  • std::string_view (for better performance)
  • std::expected (for better API)
  • compile time reflection (for more smarter inference and also cleaner API)

So we need to redesign public API with C++26 native way, and migrate code base into more modern C++.

In another way, I suggest below tasks

  • Migrate internal code base into C++26
  • Add new public API for C++26
  • Migrate current API to C++17 (in backward compatible way) (co-exist with more modern C++26 API)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions