blocksr

Crates.ioblocksr
lib.rsblocksr
version1.0.0
sourcesrc
created_at2024-10-15 04:43:55.826763
updated_at2024-10-15 04:43:55.826763
descriptionDrew's Rust library for (clang/objc) blocks
homepagehttps://sealedabstract.com/code/blocksr
repositoryhttps://github.com/drewcrawford/blocksr
max_upload_size
id1408978
size150,955
Drew Crawford (drewcrawford)

documentation

README

Drew's Rust library for (clang/objc) blocks.

logo

This is my Rust crate for using blocks, the Apple C extension often used with ObjC. This crate may be compared with the more popular block crate.

This crate is part of the objr expanded universe universe which provide low-level, zero-cost abstractions for Apple platform features that mimic code from first-party compilers. Distinctive features of this library include:

  • Every block is a distinct newtype, creating a richer typesystem that unlocks new compile-time optimizations
    • In Rust, blocks may be FnOnce, FnMut (implemented), or Fn (planned), unlocking the full Rust typesystem
    • In C/ObjC, blocks may escape or not, unlocking various optimizations used by real C/ObjC compilers
    • C/ObjC is a giant ball of unsafe code, and most direct use of this crate is also unsafe. Bindings authors are encouraged to wrap safe API based on their local knowledge.
    • Ergonomic macros for quickly binding new platform APIs
  • The continuation feature (off by default) bridges block-based completion handlers to Rust async fns.
    • This is similar to (and informed by) Apple's own Swift bridge for async methods, with broad compatability across real-world Apple APIs.
    • This Rust version is self-contained, 200 lines, does not depend on Tokio and is tested against other async runtimes.
  • Permissively licensed

Examples

Escaping block

use blocksr::once_escaping;
once_escaping!(MyBlock (arg: u8) -> u8);
let f = unsafe{ MyBlock::new(|_arg| {
    3
})};
//pass f somewhere...

Many escaping, environment

In ObjC, blocks have a lifetime that extends beyond any single invocation, and are dropped after the block is dropped. In Rust, types cannot generally be moved into an Fn or FnMut closure, as the syntax moves them into an invocation, of which there are an arbitrary number.

Because this mismatch in usecase is quite common, the many macros have an additional component, the environment.
The environment is moved into our block as a whole upon creation, rather than any single invocation, and a reference is passed as the first argument to the closure.

In an FnMut context we can mutate the environment:

use blocksr::many_escaping_nonreentrant;
many_escaping_nonreentrant!(MyBlock (environment: &mut u8) -> ());
let f = unsafe{ MyBlock::new(23, |environment| {
    *environment += 1
})};
//pass f somewhere...

The environment is dropped when the block is dropped, with assistance from the ObjC runtime. This will occur sometime after the last execution.

Commit count: 28

cargo fmt