Funciones Inseguras (Unsafe)
Llamar Funciones Unsafe (Inseguras)
Una función o método se puede marcar como unsafe
si tiene condiciones previas adicionales que debes mantener para evitar un comportamiento indefinido:
Escribir Funciones Unsafe (Inseguras)
Puedes marcar tus propias funciones como unsafe
si requieren condiciones concretas para evitar un comportamiento indefinido.
Speaker Notes
This slide should take about 5 minutes.
Llamar Funciones Unsafe (Inseguras)
get_unchecked
, like most _unchecked
functions, is unsafe, because it can create UB if the range is incorrect. abs
is incorrect for a different reason: it is an external function (FFI). Calling external functions is usually only a problem when those functions do things with pointers which might violate Rust’s memory model, but in general any C function might have undefined behaviour under any arbitrary circumstances.
En este ejemplo, "C"
es la ABI.; también hay otras ABI disponibles.
Escribir Funciones Unsafe (Inseguras)
We wouldn’t actually use pointers for a swap
function - it can be done safely with references.
Note that unsafe code is allowed within an unsafe function without an unsafe
block. We can prohibit this with #[deny(unsafe_op_in_unsafe_fn)]
. Try adding it and see what happens. This will likely change in a future Rust edition.