status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
Page: Naming concentions (reusing spec names)
Pages
Accidental slashing protection techniques Analyzing testnets data Developer tips & tricks Home Log levels Memory allocation pitfalls Naming concentions (reusing spec names) Profiling Proof of Stake fork choice notes RPC cookbook Release process SystemD setup for running a Nimbus beacon node The macro skeptics guide to the p2pProtocol macro Tracking Eth2.0 specs inefficiencies networking flow
0 Naming concentions (reusing spec names)
Mamy Ratsimbazafy edited this page 2019-11-28 11:26:45 +01:00
Table of Contents

Naming convention

Ethereum Foundation uses:

  • snake_case for fields and procedure names
  • MACRO_CASE for constants
  • PascalCase for types

Nim NEP-1 recommends:

  • camelCase for fields and procedure names
  • PascalCase for constants
  • PascalCase for types

To facilitate collaboration and comparison, nim-beacon-chain uses the Ethereum Foundation convention.