Michael Sproul 3412a3ec54 Remove saturating arith from state_processing (#1644) ... ## Issue Addressed Resolves #1100 ## Proposed Changes * Implement the `SafeArith` trait for `Slot` and `Epoch`, so that methods like `safe_add` become available. * Tweak the `SafeArith` trait to allow a different `Rhs` type (analagous to `std::ops::Add`, etc). * Add a `legacy-arith` feature to `types` and `state_processing` that conditionally enables implementations of the `std` ops with saturating semantics. * Check compilation of `types` and `state_processing` _without_ `legacy-arith` on CI, thus guaranteeing that they only use the `SafeArith` primitives 🎉 ## Additional Info The `legacy-arith` feature gets turned on by all higher-level crates that depend on `state_processing` or `types`, thus allowing the beacon chain, networking, and other components to continue to rely on the availability of ops like `+`, `-`, `*`, etc. **This is a consensus-breaking change**, but brings us in line with the spec, and our incompatibilities shouldn't have been reachable with any valid configuration of Eth2 parameters.		2020-09-25 05:18:21 +00:00
..
workflows	Remove saturating arith from state_processing (#1644)	2020-09-25 05:18:21 +00:00
ISSUE_TEMPLATE.md	Github: Add version to issue template (#937)	2020-03-20 12:18:31 +11:00
PULL_REQUEST_TEMPLATE.md	Add PR and issue templates	2018-10-14 14:51:59 +11:00