-
Notifications
You must be signed in to change notification settings - Fork 60
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
Standardise conventions for comments and naming in Kernel #858
Comments
Agreed! In terms of naming, a few things that I noticed:
|
@Fumuran - this is largely done already, right? Or is there something remaining? |
The ABI PR mostly addressed the format of the comments and procedures, but I think there are still some ambiguity in naming, I'm not sure that we updated the usage of hash/commitment terms. |
@Fumuran - could you create a more targeted issues for naming? Then we can close this one. Re hash vs. commitment - I think we should try to move away from hash toward commitment. |
Created an issue: #1092 |
Feature description
Throughout the kernel different conventions for comments and naming have been used, e.g. in account.masm:
miden-base/miden-lib/asm/kernels/transaction/lib/account.masm
Lines 360 to 362 in 7ede403
miden-base/miden-lib/asm/kernels/transaction/lib/account.masm
Line 376 in 7ede403
miden-base/miden-lib/asm/kernels/transaction/lib/account.masm
Lines 528 to 529 in 7ede403
miden-base/miden-lib/asm/kernels/transaction/lib/account.masm
Lines 421 to 423 in 7ede403
This is an isolated example with
panics
but it can be seen in documentation comments, naming of return values, etc...Why is this feature needed?
We need to make sure that the code is clean, readable and understandable.
Furthermore setting the right conventions early will enable the project to scale easier.
The text was updated successfully, but these errors were encountered: