Page "Cyclone (programming language)" Paragraph 32

Although the person who wrote the function could have inserted checks, let us assume that for performance reasons they did not.

Calling will result in undefined behavior ( typically, although not necessarily, a SIGSEGV being sent to the application ).

To avoid such problems, Cyclone introduces the pointer type, which can never be.

Thus, the " safe " version of would be: