We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We allow ourselves the use of GCC extensions, such as attribute((cleanup)) to simplify control flow due to temporary allocations.
This should be documented, including the replacement of the common "if (error) goto out;" idiom with "if (error) return;"
Then all code should be cleaned up to use this pattern. This might need extensions to libgsystem, or a more local approach.
The text was updated successfully, but these errors were encountered:
I don't think rewriting everything to be consistent is going to happen. The use of the cleanup attribute is primarily a coding style in the backend.
Sorry, something went wrong.
No branches or pull requests
We allow ourselves the use of GCC extensions, such as attribute((cleanup)) to simplify control flow due to temporary allocations.
This should be documented, including the replacement of the common "if (error) goto out;" idiom with "if (error) return;"
Then all code should be cleaned up to use this pattern. This might need extensions to libgsystem, or a more local approach.
The text was updated successfully, but these errors were encountered: