You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an exported go function with a string return type, returns an empty string. It actually ends up sending nil to the objective-c side.
However if one tries to read the string from the swift side it results in an error because it attempts to force unwrap a nil value. There also doesn't seem to be any way to test for nil before accessing the property.
This results in having to modify functions to return the string and also an error if that string is empty, and the client side first checks the error and can then read the string, which is none to convenient
I am using this direclty in Swift 2.0 and not using objective-c, so it could be an issue there.
The text was updated successfully, but these errors were encountered:
If an exported go function with a string return type, returns an empty string. It actually ends up sending nil to the objective-c side.
However if one tries to read the string from the swift side it results in an error because it attempts to force unwrap a nil value. There also doesn't seem to be any way to test for nil before accessing the property.
This results in having to modify functions to return the string and also an error if that string is empty, and the client side first checks the error and can then read the string, which is none to convenient
I am using this direclty in Swift 2.0 and not using objective-c, so it could be an issue there.
The text was updated successfully, but these errors were encountered: