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
After extensive use internally, I feel strongly that we should change that to remove the variadic nature of msgs.
Send(context.Context, func(), Message[T]) error
We simply haven't made use of the multi-message send enough, and the ability to omit messages entirely calling send is awkward and leads to weird questions around implementation like "do I have to handle the empty messages case?"
The new API will support evolution through adding functional variadic options without breaking builds later on, if they become necessary.
Most importantly, it would make implementing destinations far far simpler.
The text was updated successfully, but these errors were encountered:
Send currently looks like this:
kawa/types.go
Line 113 in cac41ab
After extensive use internally, I feel strongly that we should change that to remove the variadic nature of msgs.
We simply haven't made use of the multi-message send enough, and the ability to omit messages entirely calling send is awkward and leads to weird questions around implementation like "do I have to handle the empty messages case?"
The new API will support evolution through adding functional variadic options without breaking builds later on, if they become necessary.
Most importantly, it would make implementing destinations far far simpler.
The text was updated successfully, but these errors were encountered: