MDEV-35438 Annotate InnoDB I/O functions with noexcept #3640
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow up to innobase/{lock0lock,dict0dict}: add
noexcept
to lock/unlock methods #3531.Description
Most InnoDB functions do not throw any exceptions, not even indirectly
std::bad_alloc
, which could be thrown by a C++ memory allocation function. Let us annotate many functions withnoexcept
in order to reduce the code footprint related to exception handling.Release Notes
This is a minor change that does not need to be documented.
How can this PR be tested?
This low level code should be well covered by the existing regression tests.
Basing the PR against the correct MariaDB version
main
branch.PR quality check