Felix Deimel

Example: **C# Interfaces**: ``` public interface ILifeform { int getAge(); } public interface IHuman: ILifeform { string getName(); } ``` **Swift Protocols**: ``` public protocol ILifeform: DNObject { func getAge()...

That won't work because we can't do multiple inheritance for the Impls (in case an interface conforms to multiple other interfaces). What we can do instead is make the Impls...

[Workaround](https://github.com/royalapplications/beyondnet/pull/62) is now in place until an Xcode update which fixes the issue is out.

We could further improve the code by resolving symlinks on macOS using [`[NSString stringByResolvingSymlinksInPath]`](https://developer.apple.com/documentation/foundation/nsstring/1417783-stringbyresolvingsymlinksinpath?language=objc). For reference, here's a quick POC showing how to call ObjC from C#: https://github.com/lemonmojo/SimpleDotNETObjCInterop There's now...

Another problem here is that .NET 8 RC1's NativeAOT doesn't play nice with Xcode 15's new linker. See https://github.com/dotnet/runtime/issues/92491. As [mentioned here](https://github.com/dotnet/runtime/issues/92491#issuecomment-1732661183), we worked around this by adding `-ld_classic` as...

`-ld_classic` is not required with RC2 anymore so the workaround has been removed in https://github.com/royalapplications/beyondnet/commit/e1336106d4a7ba6df72473f79cfc9d5347bc1cdb.

I haven't yet tested if Xcode 15.1 Beta fixes the symlink issue with xcodebuild. I'll check when 15.1 is released.

Still not fixed in Xcode 15.1

Note to self: Test again with Xcode 16 Beta

See https://github.com/dotnet/runtime/issues/88286