diff options
author | Marc Mutz <marc.mutz@kdab.com> | 2014-12-26 21:43:40 +0100 |
---|---|---|
committer | Marc Mutz <marc.mutz@kdab.com> | 2015-01-10 08:42:47 +0100 |
commit | 35915e90f61e02b9fba75bab620c29f2b7f4bc18 (patch) | |
tree | 65a26500bae9bd7ccf134f8489b879168e592184 /qtbase.pro | |
parent | 076148c7dd9de01eb1224e20223d44f5c357ed6b (diff) |
QModelIndex: plaster API with Q_DECL_NOTHROW
This is mostly straight-forward, but some things are worth noting:
1. Yes, this is necessary. The noexcept operator looks for noexcept tagging,
not at the contents of the function to determine whether to return true.
The more conditionally-noexcept functions are used, the more important it
becomes that low-level classes are correctly marked noexcept. In that, it
is like constexpr.
2. The functions that actually call into the model (data(), flags(), sibling(),
...) can throw (bad_alloc, if nothing else).
Consequently, they're not marked nothrow. They're the only ones.
Change-Id: Id0413212b0f1c049a339480ee449a53c3ca9fea0
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Diffstat (limited to 'qtbase.pro')
0 files changed, 0 insertions, 0 deletions