fix incorrect defer exit(err) statements #93
Merged
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.
When calling a function directly from a
defer
statement, like so:The
exit
function is passed theerr
variable by value, which meansthat the value of
err
will always be nil above.In order to have the deferred
exit
function use the value of theerr
variable on exit of the function, you need to wrap the
exit
callinside a temporary function, like so:
See here for more information about this odd behaviour:
https://stackoverflow.com/questions/42703707/when-defer-func-evaluates-its-parameters
The alternative solution here was to change
exit
's call signature toaccept a
*error
instead of anerror
, however we have code out therein the controllers that would break if we changed
exit
's functionsignature.
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.