|
|
|
|
|
|
by Pharohbot
4030 days ago
|
|
|
As stated before in this thread, there _will_ be nil Checks in the future which will result in NilErrors or you can just annotate it with `not nil` right now and it will never be nil. You can also use -fsanitize flags with the clang backend to trap the null dereferences. |
|
|