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.

Sign up for GitHub

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

Jump to bottom

a solution should be found for hardfork and upgrading #3302

Open

vang1ong7ang opened this issue Jun 7, 2024 · 0 comments

Contributor

vang1ong7ang commented Jun 7, 2024

the hardfork coding style is introduced because it's necessary for neo to ensure the safety when upgrading (see #2910 and #3233)

but it's not a good solution in my opinion

developers struggle to adhere to the current hardfork coding style
the increasing number of HF_XXXs complicates code maintenance and introduces critical risks during future upgrades
it slows down the process of applying hotfixes to the Neo core. For example, if many changes are based on an upcoming HF_DEFG and a critical bug requires an urgent hotfix, this can lead to conflicts with HF_DEFG

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment