Skip to content

Define constraints on membership weights #463

Description

@matejpavlovic

I thought about that a bit, and realized that I don't see any fundamental reason to disallow any set of weights. The only exception is all weights in a membership being zero, which we probably do need to treat as a special case. I see 2 options here:

  1. Declare such a membership invalid and complain / ignore it / crash / ...
  2. Treat it as a special case and pretend that all weights are 1. I can imagine this being convenient for implementations that simply don't want to deal with any vote weights - it automatically falls back into counting nodes. However, it introduces additional complexity not just in code, but especially in the semantics.

Originally posted by @matejpavlovic in #459 (comment)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions