binding-tools-for-swift
binding-tools-for-swift copied to clipboard
xamarin
We don't really use those really, so consider just using the `-C` arg and simplifying all the code to just use search paths. Why were they needed? For compiling references...
Welcome to Binding Tools for Swift (BTFS)! While much of the infrastructure and binding tooling is complete, there is number of items we expect to work on before integrating with...
Change SOM_PATH references to BTFS_PATH. We're not Swift-o-Matic anymore.
ModuleInventory.ClassesForName (SwiftName modName), ModuleInventory.ProtocolsForName (SwiftName modName), and ModuleInventory.FunctionsForName (SwiftName modName) should return public classes. Issue: Sometimes it gives us internal or private classes as well Example, from libswiftCore.dylib: - Swift._UnicodeEncoding...
A list of things that DylibBinder cannot handle: - Accurate public or private names - Unavailable - Obsoleted - Deprecated - Subscripts - Order of AssociatedTypes is not consistent with...
In DynamicXmlTests - TestGenericMethodInGenericClass the Generic parameters get a little wonky. **DylibBinder's xml** ``` ``` **SwiftInterfaceParser's xml** ``` ``` **Error:** // wrong signature //Expected string length 48 but was 43....
Protocols still need a good amount of work - self (DynamicXmlTests - DetectsSelfEasy, DetectsSelfEasy1, DetectsSelfInTuple, DetectsSelfInOptional, DetectsSelfInBoundGeneric, DetectsSelfInClosure)
Need to look over the difference between the two and how to handle them Fails DynamicXmlTests - TestConvenienceCtor
I guess not all constructors are meant to be inout? Example) DynamicXmlTests TestCtorType