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
I think passing struct isn't a efficient way. Then, my vim warning me "copy locks"
becuse struct Message and MessageExt anonymous inheritance sync.RWMutex
// primitive/message.gotypeMessagestruct {
// other codes mutex sync.RWMutex
}
// ...typeMessageExtstruct {
Message// other codes
}
will be better, if it will not case other bug. If it's ok, I can try to change it.
The text was updated successfully, but these errors were encountered:
ShannonDing
changed the title
How about change TransactionListener's method param type from struct to pointer
[Native]How about change TransactionListener's method param type from struct to pointer
Dec 31, 2019
Thank you @Me1onRind , your are right, a pointer is better. could you create a Pull Request for the issue before next Monday(we wiil release rc version in next week) if possible
Sorry I am busy these day, and see the message now (>_<), So I can't finished it before Monday now. It not in next rc version may not bad thing, may just change it to pointer may bring some unpredictable hidden bug?
When I try use transaction, I implement the interface, I find the interface method's param is struct
I think passing struct isn't a efficient way. Then, my vim warning me "copy locks"
becuse struct Message and MessageExt anonymous inheritance sync.RWMutex
So I think mabey change TransactionListener to
will be better, if it will not case other bug. If it's ok, I can try to change it.
The text was updated successfully, but these errors were encountered: