Skip to content
This repository has been archived by the owner on Nov 22, 2023. It is now read-only.

Nullable Project #516

Closed
shargon opened this issue Nov 9, 2023 · 5 comments
Closed

Nullable Project #516

shargon opened this issue Nov 9, 2023 · 5 comments
Assignees

Comments

@shargon
Copy link
Member

shargon commented Nov 9, 2023

In a blockchain virtual machine project, configuring the C# code as nullable is crucial for several reasons. Firstly, the nullable reference types feature in C# enhances code safety by providing more explicit information about the presence or absence of values. This is particularly significant in a blockchain setting where data integrity is paramount.

Secondly, the nullable feature helps in preventing null reference exceptions, a common source of runtime errors, by enforcing stricter null checks. This is vital for maintaining the stability and reliability of the virtual machine, ensuring that unexpected null values don't disrupt its operation.

Additionally, nullable reference types contribute to code clarity and maintainability. By explicitly declaring whether a variable can be null, developers can better understand and communicate the intended behavior of the code. This is especially valuable in large-scale projects like blockchain virtual machines, where multiple developers may collaborate, and code comprehension is crucial for effective teamwork.

In summary, configuring C# code as nullable in a blockchain virtual machine project promotes safety, stability, and maintainability, fostering a more robust and error-resistant codebase.

Reference:

@shargon shargon self-assigned this Nov 9, 2023
@roman-khimov
Copy link
Contributor

Gone are the days when people were typing each and every letter in each and every word of their texts...

@shargon
Copy link
Member Author

shargon commented Nov 9, 2023

Gone are the days when people were typing each and every letter in each and every word of their texts...

In other words is: we need nullable everywhere 🤣 but neo-project/neo#2955 point 2 said: "in detail".

@Jim8y
Copy link
Contributor

Jim8y commented Nov 10, 2023

either in a way to make sure no duplicate work, or have prs unmerged for 3 years. i feel the pain to describe the solution before coding, but i also feel the pain when developers complain neo core and leave the neo ecosystem.

@Jim8y
Copy link
Contributor

Jim8y commented Nov 10, 2023

I support nullable

@shargon
Copy link
Member Author

shargon commented Nov 17, 2023

This is already nullable hahha, neo don't xD

@shargon shargon closed this as completed Nov 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants