Skip to content

Conversation

fekir
Copy link
Contributor

@fekir fekir commented Aug 19, 2017

Hi,

there are a couple of method marked as noexcept, but in reality they may throw an exception.

The first method is Column::getString, since std::string needs to allocate memory, the constructor may fail and throw an exception

The second method is Database::setBusyTimeout, internally if the operation fails an exception is thrown.

I was going to remove the noexcept specifier from the destructors, since they are all noexcept if not stated otherwise, but maybe you preferred to state it explicitely, and since it does not make any difference from the language perspective, I leaved them.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 96.231% when pulling db156e6 on fekir:remove_noexcept into 670d710 on SRombauts:master.

@SRombauts SRombauts merged commit 926ebda into SRombauts:master Aug 21, 2017
@SRombauts
Copy link
Owner

Thanks @fekir, I am a bit ashamed by the setBusyTimeout() mistake!

@fekir fekir deleted the remove_noexcept branch August 21, 2017 15:10
@fekir
Copy link
Contributor Author

fekir commented Aug 21, 2017

Would you accept a pull request that removes the unnecessary noexcept from destructors (and nothrow comment)?

@SRombauts
Copy link
Owner

gladly!

@SRombauts SRombauts self-assigned this Aug 22, 2017
@SRombauts SRombauts added the bug label Aug 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants