We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NposSolver
Currently, the NposSolver::weight() trait is generic over a frame_election_provider_support::WeightInfo which returns the weights of running two flavors of phragmen.
NposSolver::weight()
frame_election_provider_support::WeightInfo
This means that the NposSolver trait is not ergonomic for developer who'd like to use their own election algorithm. We could either:
i) refactor NposSolver to be more generic; or ii) add a new trait ElectionSolver that is completely agnostic wrt to the election algorithm used.
ElectionSolver
The text was updated successfully, but these errors were encountered:
Related to paritytech/substrate#8250 and paritytech/substrate#12588
@kianenigma as discussed, this is probably not very important, but opening this issue for idea bookeeping.
Sorry, something went wrong.
No branches or pull requests
Currently, the
NposSolver::weight()
trait is generic over aframe_election_provider_support::WeightInfo
which returns the weights of running two flavors of phragmen.This means that the
NposSolver
trait is not ergonomic for developer who'd like to use their own election algorithm. We could either:i) refactor
NposSolver
to be more generic; orii) add a new trait
ElectionSolver
that is completely agnostic wrt to the election algorithm used.The text was updated successfully, but these errors were encountered: