Mark Metal as automatically safe

Author: madsmtm

examples/metal/default_xcode_game/renderer.rs

@@ -167,7 +167,7 @@ fn load_pipeline_state(
 }
 
 fn load_vertex_descriptor() -> Retained<MTLVertexDescriptor> {
-    let vertex_descriptor = unsafe { MTLVertexDescriptor::new() };
+    let vertex_descriptor = MTLVertexDescriptor::new();
 
     unsafe {
         let attributes = vertex_descriptor.attributes();
@@ -201,7 +201,7 @@ fn load_vertex_descriptor() -> Retained<MTLVertexDescriptor> {
 fn load_depth_state(
     device: &ProtocolObject<dyn MTLDevice>,
 ) -> Retained<ProtocolObject<dyn MTLDepthStencilState>> {
-    let depth_state_desc = unsafe { MTLDepthStencilDescriptor::new() };
+    let depth_state_desc = MTLDepthStencilDescriptor::new();
     depth_state_desc.setDepthCompareFunction(MTLCompareFunction::Less);
     depth_state_desc.setDepthWriteEnabled(true);
     device

framework-crates/objc2-metal/src/lib.rs

@@ -53,6 +53,18 @@
 //!
 //! It is yet unclear whether Metal APIs are bounds-checked on the CPU side or
 //! not, so APIs that take offsets / lengths are often unsafe.
+//!
+//! ## Threading
+//!
+//! TODO.
+//!
+//! ## Resource allocation and memory management
+//!
+//! TODO.
+//!
+//! ## Type safety
+//!
+//! TODO.
 #![recursion_limit = "256"]
 #![allow(non_snake_case)]
 #![no_std]