Steven Sheldon

Adding a method isn't ergonomic

7

Adding a method to a `ClassDecl` isn't ergonomic because you need to cast the function to a function pointer, like so: ``` rust add_method(sel!(setFoo:), my_obj_set_foo as extern fn(&mut Object, Sel,...

Consider making objc no_std compatible

1

This crate is mainly just a wrapper around the objc runtime dylib, so it shouldn't need much else. If we can make it `no_std` then it might be usable in...

mem::swap doesn't work with Objects

6

For example, the following code: ``` rust let mut a: Id = INSString::from_str("a"); let mut b: Id = INSString::from_str("b"); println!("{} {}", a, b); mem::swap(a.deref_mut(), b.deref_mut()); println!("{} {}", a, b); ```...

API for passing already nul-terminated strings to avoid allocation

1

Currently, in the runtime and declare modules, the API takes `&str` for ease of use. However, this requires copying the string into a buffer and adding a nul terminator byte....

Implementing derive for custom structs is tedious, but all the information it needs is in the declaration of the struct: the name, and the type and order of its members....

I believe that, currently, `Object`, `Class`, etc are `Send` and `Sync` because they don't contain any types to specify otherwise. Is this correct? At least, it seems like not all...

Implement Encode for more types

1

`Encode` should be implemented for more types. For example, it currently doesn't support pointers to many value types; this could easily be added for all value types, except it'd conflict...

Generating schemes with BuildableProductRunnable for watchOS targets causes errors in Xcode 14 beta

4

With an example `project.yml` like this: ``` yaml name: Foo targets: Foo: type: framework platform: watchOS schemes: Foo: build: targets: Foo: build ``` And performing the following steps: ``` xcodegen...

There are more fields returned in the v3 business that aren't exposed by the current `YLPBusiness`: * `is_closed` * `price` * `photos` * `hours` Note that these fields are only...

There are more parameters accepted by the v3 search API that aren't supported by the current `YLPQuery`, including: * `locale` * `price` filter * `open_now` and `open_at` filters * `attributes`...