Go:readonly Variable

This is a creation in Article, where the information may have evolved or changed.

The absence of read-only variables should be considered "design flaws" in the Go language. For example, the default is to use an error instance to determine the category of errors, but these exportable global variables can actually be externally modified, then there is a hidden risk.

In the actual development, there are many memory-sensitive data that need to be set to access, including read-only, write-only, or non-operational, but can be implemented with Syscall.

Examples of Use:

Of course, more functionality can be achieved on this basis, similar in principle. For sensitive data, you should also add the following features:

1. Authentication: Use runtime. Caller validates the call stack, allowing only the specified function call.

2. Memory Lock: With Syscall. Mlock locks data on physical memory pages and disables swapping to hard disks.

Latest news, please scan the code attention