diff options
| author | Teddy Wing | 2018-08-23 10:22:14 +0200 |
|---|---|---|
| committer | Teddy Wing | 2018-08-23 10:27:16 +0200 |
| commit | ba97dc5f57da049f9cada870000bffe556dec38a (patch) | |
| tree | af047f423523cb3cfe1e88754c4bca4b1af1f425 /src/lib.rs | |
| parent | b33feb5c94bf346ddc5dee68c7bf8c6b039168db (diff) | |
| download | dome-key-map-ba97dc5f57da049f9cada870000bffe556dec38a.tar.bz2 | |
cocoa_bridge: Continue outline of Objective C callable
Add some more structure to the function that will be called from
Objective C code.
* Give it a name, `parse_mappings` (not very thoroughly considered)
* Initialise some Foundation data structures to mirror our Rust ones
* Add the beginning of a struct that will be the ObjC version of our
`MapGroup` struct, containing `NSDictionary`ies.
* Move the `extern crate` into `lib.rs`, I keep forgetting that's where
they go.
* Add a test that just calls `parse_mappings` to check that the code
compiles.
parser::MapGroup:
Make both its fields public to enable us to access them from
`cocoa_bridge`.
Used this helpful example as a reference for the Rust Cocoa code:
https://github.com/servo/core-foundation-rs/blob/c99c05c/cocoa/examples/hello_world.rs
Diffstat (limited to 'src/lib.rs')
| -rw-r--r-- | src/lib.rs | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -1,3 +1,5 @@ +extern crate cocoa; + #[macro_use] extern crate combine; |
