#osx #ios #objective-c #blocks

block

Rust interface for Apple’s C language extension of blocks

9 releases

0.1.6 May 8, 2016
0.1.5 Apr 4, 2016
0.1.4 Nov 12, 2015
0.1.2 Oct 10, 2015
0.0.1 Apr 17, 2015

#8 in macOS APIs

Download history 1537/week @ 2018-12-04 1714/week @ 2018-12-11 1421/week @ 2018-12-18 1486/week @ 2018-12-25 1677/week @ 2019-01-01 2001/week @ 2019-01-08 1534/week @ 2019-01-15 2032/week @ 2019-01-22 2081/week @ 2019-01-29 1910/week @ 2019-02-05 2334/week @ 2019-02-12 2511/week @ 2019-02-19 2463/week @ 2019-02-26 2081/week @ 2019-03-05 2536/week @ 2019-03-12

3,124 downloads per month
Used in 320 crates (9 directly)

MIT license

16KB
290 lines

Rust interface for Apple's C language extension of blocks.

For more information on the specifics of the block implementation, see Clang's documentation: http://clang.llvm.org/docs/Block-ABI-Apple.html

Invoking blocks

The Block struct is used for invoking blocks from Objective-C. For example, consider this Objective-C function:

int32_t sum(int32_t (^block)(int32_t, int32_t)) {
    return block(5, 8);
}

We could write it in Rust as the following:

unsafe fn sum(block: &Block<(i32, i32), i32>) -> i32 {
    block.call((5, 8))
}

Note the extra parentheses in the call method, since the arguments must be passed as a tuple.

Creating blocks

Creating a block to pass to Objective-C can be done with the ConcreteBlock struct. For example, to create a block that adds two i32s, we could write:

let block = ConcreteBlock::new(|a: i32, b: i32| a + b);
let block = block.copy();
assert!(unsafe { block.call((5, 8)) } == 13);

It is important to copy your block to the heap (with the copy method) before passing it to Objective-C; this is because our ConcreteBlock is only meant to be copied once, and we can enforce this in Rust, but if Objective-C code were to copy it twice we could have a double free.

No runtime deps