Skip to content

docs: note C++20 library dialect in FAQ C++ rationale #2934

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
julianoes merged 1 commit into from
Jul 15, 2026
Merged

docs: note C++20 library dialect in FAQ C++ rationale #2934

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/en/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
## Why was the core of MAVSDK written in C++?

The aim was to have an API in a language which is cross-platform and has many language bindings.
The library also needs to be lightweight and fast, so it does not slow down for onboard usage at higher rate messaging.
The core library is maintained as modern C++ (currently **C++20**; see `CMAKE_CXX_STANDARD` in `cpp/src/CMakeLists.txt`) and needs to remain lightweight and fast so it does not slow down for onboard usage at higher rate messaging.
Additionally, MAVSDK should be able to run efficiently in embedded setups, e.g. as part of an app or onboard a drone on a companion computer, as well as provide a simple and safe API. This favoured C++ over C as it allows for more expressive but type-safe APIs using standard library containers (e.g. `std::vector<MissionItem>`) for usage in embedded setups.

## Are multiple vehicles supported?
Expand Down
Loading