-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Remove score_update_worst_case
default impl
#12043
Conversation
Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
The CI pipeline was cancelled due to failure one of the required jobs. |
Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
unimplemented!(); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unimplemented!(); | |
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I'm with Shawn here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed it.
Actually i dont get what this fixes. if the feature flag is not there, the whole function wont be there? what does it matter if there is a default impl? |
It happens since the feature of the crate which contains the trait is enabled, but the one which should implement is not. |
unimplemented!(); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I'm with Shawn here.
Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
Now the messed up features make Polkadot not build 💩 |
Do not ever default impl feature gated trait functions, unless you want very weird stuff to happen.
Reason being is that someone will forget to enable the feature and you use the default impl without noticing.
#11976 should fix this permanently.