defer func() { if r := recover(); r != nil { ("Recovered:", r) } }()
Anywhere that involves array value, you should write a catch throw exception at the beginning
The problem of array cross-border is most likely to cause exceptions, and the entire program will be terminated without throwing it.
The array is out of bounds. Simply put, the program tries to access elements that do not exist in the array. This behavior can cause program runtime errors and even crashes. In Go language, array out-of-bounds exceptions are usually caused by the following situations:
- Index calculation error: A programmer encountered a logical error when calculating the array index.
- Boundary condition omission: In loop or condition judgment, the boundary condition of the array is not correctly processed.
- Improper external input: User input or external data causes the index value to exceed the range of the array.
Reference Documents
What are the scenarios where Go language triggers exceptions
- Arrays cross bounds
- Null pointer access
- Type assertion failed
- Divider is zero
- Error caused by concurrent access to map
- Stack Overflow
- Other potential trigger exception scenarios
- Uninitialized variable usage
- Illegal type conversion
- Resource leakage or improper management
- Deadlock