@vfaronov The use case was regarding your comment: > Do you think it’s safe to assume that navqueue_go_back will never be exposed > in the plugin API, for example?
With an assertion, if it gets added to the plugin API and we forget to update the code (@kugel- said "No, but things can be fixed at that point."), it will raise the assertion and make it easier for core/plugin devs to debug (using GDB), it will bail right where the precondition is violated rather than causing a segmentation fault (or worse, not causing one) later on in the code after the programming error. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/1537#issuecomment-315500213
