This repository was archived by the owner on Sep 30, 2024. It is now read-only.
This repository was archived by the owner on Sep 30, 2024. It is now read-only.
Do not use safe and unsafe to describe pointer types. #14
Description
This issue was copied from checkedc/checkedc#14
We have been using the terminology safe and unsafe to describe the new
pointer types and the existing C pointer type, respectively. The term
unsafe has negative connotations. The term safe is also imprecise. The
design only addresses bounds safety and does not yet address memory
lifetime safety or type casts that allow corruption of bounds information.
We are switching to the terms checked and unchecked instead.
This mostly addresses issue #11. We still need to make sure that we are
being clear in the text about what is not being checked.