Mads Marquart

> I just tested with v0.30.9 and I’m seeing the exact same warning right as the very first log message. Thanks. Then this is indeed a new warning. I'm working...

Also discussed previously in the `metal` crate: https://github.com/gfx-rs/metal-rs/issues/190

I think we should stick with Objective-C naming at the very least until we can autogenerate documentation based on https://developer.apple.com/, since it's just much more discoverable that way - but...

The [`windows` crate](https://github.com/microsoft/windows-rs) is also a good place to look to for how this is done elsewhere.

> instance method and type method I'm a bit unsure about your terminology here; do you mean "instance method" and "protocol method"? --- In general **my opinion** is that adding...

Another possibility is to namespace enums, structs and typedefs behind modules (when it makes sense): - Enum: `mod ns_accessibility { struct AnnotationPosition(NSInteger) }` - Struct: `struct NSDirectionalEdgeInsets { fields* }`...

[`cidre`](https://github.com/yury/cidre) uses the following scheme: ```rust mod ns { struct Array; // NSArray struct String; // NSString struct Number; // NSNumber } // Usage use cidre::ns; let array: ns::Array =...

I've pushed some of the `objc2::runtime` types towards a more Swifty naming scheme in https://github.com/madsmtm/objc2/pull/463.

I've pondered this for a while now, but at this point I feel like sticking close to Objective-C for method and function names is the correct approach, even though it's...

I've implemented the better enum case prefix stripping in https://github.com/madsmtm/objc2/commit/a305d6f7779675524b65dc4e89866cb5c44f134f.