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
ExchangeContext::SendMessage takes a flags arg of type SendFlags, which is a BitFlags<SendMessageFlags>
That means every call to this API has an arg that looks like SendFlags(SendMessageFlags:kSomething).
Proposed Solution
It looks like the BitFlags constructor that takes the enum value is explicit, but we could add overloads of SendMessage that take SendMessageFlags directly as a last arg to cut down on the extra verbosity at callsites.... Callsites that need more than one flag will still need to do something, of course (though if we wanted to we could make these overloads variadic templates that pass through all the remaining args to the SendFlags ctor.
The text was updated successfully, but these errors were encountered:
Problem
ExchangeContext::SendMessage takes a flags arg of type
SendFlags
, which is aBitFlags<SendMessageFlags>
That means every call to this API has an arg that looks like
SendFlags(SendMessageFlags:kSomething)
.Proposed Solution
It looks like the
BitFlags
constructor that takes the enum value isexplicit
, but we could add overloads ofSendMessage
that takeSendMessageFlags
directly as a last arg to cut down on the extra verbosity at callsites.... Callsites that need more than one flag will still need to do something, of course (though if we wanted to we could make these overloads variadic templates that pass through all the remaining args to theSendFlags
ctor.The text was updated successfully, but these errors were encountered: