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
With the SUM_OF_MEMBERS semantics, the maximum weight of individual members is no longer implied by the maximum weight of a group. However, probably most switches can't faithfully support arbitrary weights (or even up to the int32 type that we use to represent weights). I propose to change the SelectorSizeSemantics in action profiles to be a oneof where sum_of_members can contain its max_member_weight.
Ideally, sooner rather than later, since we just finished adding these semantics, so hopefully no one is using them yet.
The text was updated successfully, but these errors were encountered:
@antoninbas and @smolkaj, any thoughts on how to include this additional semantics in the annotation? Just @selector_size_semantics(SUM_OF_MEMBERS, )? Then we'd presumably want the same for SUM_OF_WEIGHTS? @selector_size_semantics(SUM_OF_WEIGHTS, <ignore this value?>)
With the SUM_OF_MEMBERS semantics, the maximum weight of individual members is no longer implied by the maximum weight of a group. However, probably most switches can't faithfully support arbitrary weights (or even up to the int32 type that we use to represent weights). I propose to change the
SelectorSizeSemantics
in action profiles to be a oneof where sum_of_members can contain its max_member_weight.Ideally, sooner rather than later, since we just finished adding these semantics, so hopefully no one is using them yet.
The text was updated successfully, but these errors were encountered: