Chinedu Francis Nwafili
Chinedu Francis Nwafili
Right now we 1. Duplicate the mesh/armature 2. Convert the copy's bones into FK The problem is that the copy has bones named like `Bone.001` which forces you to write...
At the time of this issue all collada files in the test suite are from Blender exports. We'll want to add tests for collada files exported from Maya (and other...
Right now if a struct has a small number of fields we default to using an enum to encode the delta. Something like: ```rust // We don't use generics in...
## Problem The following should not compile since we're saying `#[swift_bridge(get_with(&name = Clone::clone))]` instead of `#[swift_bridge(get_with(&events = Clone::clone))]` But it does.. and leads to undefined behavior if you call the...
For example, the following does not work right now: ```rust #[swift_bridge::bridge] mod ffi { extern "Rust" { fn some_function(arg: Vec) -> Vec; } } ```
The following currently panics: ```rust #[swift_bridge::bridge] mod ffi { extern "Rust" { type SomeType; #[swift_bridge(init)] fn new(); } } ``` We should instead have a compile time error that underlines...
We renamed `into_return_type` to `return_into` in #71 We're temporarily adding `into_return_type` back in https://github.com/chinedufn/swift-bridge/pull/95 so that we can make more non-breaking releases on the `0.1.x` semver train.
Add support for a dot `.` notation that lets us expose nested fields. For example, the following should be possible: ```rust #[swift_bridge::bridge] mod ffi { extern "Rust" { type SomeType;...
Something like: ```rust struct MyStruct { field1: A, field2: B, } #[swift_bridge::bridge] mod ffi { extern "Rust" { type MyStruct; #[swift_bridge(associated_to = MyStruct)] fn new() -> MyStruct; } } ```...
Given the following bridge: ```rust #[swift_bridge::bridge] mod ffi { extern "Rust" { #[swift_bridge(Hashable)] type SomeType; } } #[derive(Hash, PartialEq, Eq, PartialOrd, Ord)] struct SomeType; ``` We should emit some Swift...