Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Removing static initialization of nano::network_params #3413

Merged
merged 17 commits into from
Aug 6, 2021

Conversation

clemahieu
Copy link
Contributor

This is a series of commits to remove static instantiation of nano::network_params. Static initialization is a bad practice in general and prevents more complex configurations, hindered config reloading, and is generally counterintuitive.

… process and remove the subsequently unused instance of nano::network_params that was instantiated statically.
…ssary. Serializing this version number to/from the message_header the same as the other two version_max and version_using.
…r than on message header construction. This separates the assignment of protocol-specific information, specifically the version numbers, from the logic of creating messages.
…atically instantiated dev network params with the version available in the nano::dev namespace.
…instantiation of network parameters to test if a state block is an epoch.
@zhyatt zhyatt added the quality improvements This item indicates the need for or supplies changes that improve maintainability label Aug 4, 2021
@zhyatt zhyatt added this to the V23.0 milestone Aug 4, 2021
thsfs
thsfs previously approved these changes Aug 4, 2021
…work_constants in order to eliminate guesswork of setting these values before serializing.
@clemahieu clemahieu merged commit 298d38c into develop Aug 6, 2021
@clemahieu clemahieu deleted the network_params_ref branch August 6, 2021 12:44
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
quality improvements This item indicates the need for or supplies changes that improve maintainability
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants