chore: Follow rust naming convention#801
Conversation
|
@0xYYY Could you run |
|
Strange, is it really |
I'm actually not totally sure about this one. So would like your inputs on this. The guideline states that the usage of |
Yeah , could we leave this one out please |
|
Thanks for resolving the conflicts! |
* master: (28 commits) chore(ci): Add release token to enable runs against release PR (#840) feat(ssa): array sort (#754) chore: update readme (#811) chore: fix clippy (#825) chore: remove stale comment on HirFunction.unchecked_from_expr (#827) chore: Getter naming refactor (#803) chore: updated "HirFunction::unsafe_from_expr" to "HirFunction::unchecked_from_expr" (#823) chore: Forbid unsafe code (#824) chore: Follow rust naming convention (#801) feat(ci): Add concurrency group for rust workflow (#806) chore(ssa): rename impl method to follow Rust guideline (#782) fix(nargo): `nargo test` now only runs test functions defined in the current module (#805) chore(nargo): Remove outdated error message when Prover/Verifier.toml is missing (#807) chore(ssa): rename codegen to ssa_gen + reorg of `Value` struct (#797) chore(nargo): abstract paths from nargo's working directory (#761) chore(ci): Rename workflows (#804) feat: Impls with generics (#798) chore(ssa): Add doc comments on `Opcode` struct (#778) fix: operators issuing type errors when used with matching integer types arising from generic code (#789) chore(nargo)!: bump MSRV to 1.66.0 (#799) ...
Related issue(s)
Related to #780.
Description
Summary of changes
Follow the Rust API Gudeline.
Modified cases:
IRGenerator,SSAFunctionfollowing theUUID->Uuidexample.LValue,LValueRhs,HirLValuefollowing theUSize->Usizeexample.Please let me know if any of these seems inappropriate.
Dependency additions / changes
N/A
Test additions / changes
N/A
Checklist
cargo fmtwith default settings.Additional context