Skip to content

Promote warning to exception in ext/sysvsem #6013

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.

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

Closed
wants to merge 1 commit into from

Conversation

kocsismate
Copy link
Member

No description provided.

@nikic
Copy link
Member

nikic commented Aug 24, 2020

I'm unsure about this one.

@kocsismate
Copy link
Member Author

@nikic What's the problem with this one? Isn't it somewhat similar to the cases when we throw if a connection is not open? Or there are use-cases when people (have to) call sem_release() not knowing if the semaphore has already been acquired?

@nikic
Copy link
Member

nikic commented Aug 25, 2020

This seems a bit different. It's not about being not open / uninitialized, but about performing an unlock without a lock. Best analogy to other extensions we have would probably be to commit/rollback without starting a transaction.

Then again, unlock without lock does seem like a clear programming error...

@kocsismate
Copy link
Member Author

In case of doubt, then the best we can do is to close the PR :) It not a big waste.

@kocsismate kocsismate closed this Aug 25, 2020
@kocsismate kocsismate deleted the sysvsem-warning branch August 25, 2020 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants