-
Notifications
You must be signed in to change notification settings - Fork 444
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
Update ebpf comment format #4624
Conversation
Thanks for doing this! It makes the entire compiler more consistent in style. |
0a62f74
to
4c568a1
Compare
You're welcome @fruffy I'm glad to hear that it's making the compiler more consistent in style. If you have any more feedback then please let me know |
484c865
to
5848a28
Compare
Co-authored-by: Fabian Ruffy <[email protected]>
Co-authored-by: Fabian Ruffy <[email protected]>
Co-authored-by: Fabian Ruffy <[email protected]>
Co-authored-by: Fabian Ruffy <[email protected]>
Co-authored-by: Fabian Ruffy <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are still a bunch of lowercase instances and dots missing but I do not want to be too pedantic.
I have made the following changes in ebpf(backend):
Used triple slashes (///) for commenting functions and classes.
Used double slashes (//) for comments within the code.