Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

CHANGELOG: Explain what sealing means #271

Merged
merged 1 commit into from
Nov 29, 2020
Merged

CHANGELOG: Explain what sealing means #271

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,14 +39,19 @@
### Breaking Changes

- Remove `Spi::read` in favor of `transfer_split_uneven` ([#190]).
- Seal the `timer::Instance` trait ([#214]).
- Make GPIOs start in a `Disconnected` state instead of `Input<Floating>` ([#220] [#245]).
- 🦭 all `Instance` traits ([#255]).
- 🦭 PPI traits ([#259]).
- Seal¹ the `timer::Instance` trait ([#214]).
- Seal¹ all `Instance` traits ([#255]).
- Seal¹ PPI traits ([#259]).
- Various TWIM fixes and improvements - removes automatic transfer splitting ([#242]).
- Remove typestate from RTC to make it easier to use ([#252]).
- Also return owned `Pins` from `Usart::free()` ([#261]).

¹ _A trait can be sealed by making a private trait a supertrait. That way, no
downstream crates can implement it (since they can't name the supertrait).
This is just to make sure the trait isn't implemented by types that shouldn't
implement it._

### Internal Improvements

- Utilize [`cargo-xtask`] to simplify CI and the release process ([#207] [#210]).
Expand Down