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
As before we can have a private filed with unsupported named type, but in recently update(gomobile version +24a199a Wed Jan 13), it breaks this rule, that makes a huge impact to code, and make all types which want to be used for mobile narrows down to supported basic type....
Before:
The following type is working
type ABC struct {
WSClient
}
type WSClient struct {
conn *websocket.Conn
}
ABC is the struct exported for use in android.
After:
it is not working with an error message:
gomobile: unsupported named type xxxx
The text was updated successfully, but these errors were encountered:
ghost
changed the title
x/mobile/mobile: unsupported named type affects private fields
x/mobile/mobile: unsupported named type affects private fields in embedded structure
Jan 19, 2016
hyangah
changed the title
x/mobile/mobile: unsupported named type affects private fields in embedded structure
x/mobile/bind: unsupported named type affects private fields in embedded structure
Jan 21, 2016
It's because non-pointer struct type as a field is not yet supported.
I don't think it was ever working before but I may be wrong. Duplicate of #11318.
As before we can have a private filed with unsupported named type, but in recently update(gomobile version +24a199a Wed Jan 13), it breaks this rule, that makes a huge impact to code, and make all types which want to be used for mobile narrows down to supported basic type....
Before:
The following type is working
type ABC struct {
WSClient
}
type WSClient struct {
conn *websocket.Conn
}
ABC is the struct exported for use in android.
After:
it is not working with an error message:
gomobile: unsupported named type xxxx
The text was updated successfully, but these errors were encountered: