Skip to content

This year in embedded Rust #25

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.

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

Merged
merged 3 commits into from
Nov 14, 2018
Merged

This year in embedded Rust #25

merged 3 commits into from
Nov 14, 2018

Conversation

japaric
Copy link
Member

@japaric japaric commented Nov 8, 2018

This is the blog post I mentioned during the last meeting. I'd like to publish
it next Wednesday.

All kind of feedback is welcomed! Let me know if there's something you'd like to
see mentioned in this post.

Blockers for publishing this:

Additionally we might want to include these two in this post:

  • [postponed] awesome-embedded-rust: "does this compile on stable?" community effort.

What: Make an issue with instructions (add version badge to each crate in the
list?) and link to it from the blog post.

I suggested this before. @rust-embedded/resources do you want to tackle this?

  • wg: 2019 wishlist

What: Make an issue collecting people thoughts on what should we focus on next
year: ecosystem gaps that need to be filled, docs that need to be written,
unstable stuff that should prioritized for stabilization, language feature
requests.

@rust-embedded/all thoughts? we'll probably have the "call for 2019 blog post"
soon, in any case. Should we run an informal survey ourselves, or just watch
over the incoming blog posts?

@japaric japaric requested a review from a team as a code owner November 8, 2018 22:33
@therealprof
Copy link
Contributor

@japaric Reads good.

What: Make an issue with instructions (add version badge to each crate in the
list?) and link to it from the blog post.

I'm not sure how we can pull this off.

adamgreig
adamgreig previously approved these changes Nov 13, 2018
@adamgreig
Copy link
Member

This looks great! I don't have any suggestions for the post as-written, but in terms of your additional questions:

awesome-embedded-rust: "does this compile on stable?" community effort.
What: Make an issue with instructions (add version badge to each crate in the
list?) and link to it from the blog post.

I think this sounds good. At the very least we can create the issue and tag it help-wanted and then start working through crates. Hopefully crate authors themselves might be motivated to check their crate builds on stable, get it working if not, and add the tag. It might mean some PR churn but that's not too hard to handle.

wg: 2019 wishlist
What: Make an issue collecting people thoughts on what should we focus on next
year: ecosystem gaps that need to be filled, docs that need to be written,
unstable stuff that should prioritized for stabilization, language feature
requests.

👍 on including this too. It would be good to get strong targets lined up for after 2018 hits.

therealprof
therealprof previously approved these changes Nov 13, 2018
Copy link
Contributor

@therealprof therealprof left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

jamesmunns
jamesmunns previously approved these changes Nov 13, 2018
Copy link
Member

@jamesmunns jamesmunns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few minor suggestions, but overall looks great. Thank you @japaric!

days are over: Rust 1.30 marks the first stable release where you can build
fully working embedded programs without relying on unstable features.

Furthermore, we now have some [unit][] [tests] that check embedded code in the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extra []?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is to avoid this being parsed as [unit][tests] which would render as a single word / broken link.

have put a lot of effort in making the first experience as frictionless as
possible with the help of [templates] and [tooling].

[the embedded Rust book]: https://docs.rust-embedded.org/book
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: use "The Embedded Rust Book" as a proper name

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: used multiple times

targets on parity with the ARM Cortex-M target during the next year.

Here's to a 2019 with *more* embedded Rust success stories (yes, "more"; wait
for the upcoming revamped rust-lang website ;-). Happy embedded hacking!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing )

edition release we reflect on our progress and share our achievements with you
in this post.

[embedded WG]: https://github.com/rust-embedded/wg
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: "Embedded WG" as a proper name

@japaric japaric dismissed stale reviews from jamesmunns, therealprof, and adamgreig via 788b35e November 14, 2018 00:35
@japaric
Copy link
Member Author

japaric commented Nov 14, 2018

addressed @jamesmunns comments and mentioned the 2019 wishlist survey at the end.

re-r? @rust-embedded/resources

Copy link
Member

@jamesmunns jamesmunns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@jamesmunns
Copy link
Member

@japaric do you want to merge and publish this today? Also do you want to add links to the normal "discuss on ..." channels of twitter/reddit/u.r-l.o?

@japaric
Copy link
Member Author

japaric commented Nov 14, 2018

@jamesmunns yes and yes. Can I task you with the publishing and posting this to social media?

@jamesmunns
Copy link
Member

Will merge/publish shortly, post everywhere, then submit a PR with links.

@japaric
Copy link
Member Author

japaric commented Nov 14, 2018

@jamesmunns Thanks! I've temporarily disabled branch protection so you can directly commit the new links. (I will be away for ~1h and won't be able to review / r+ your PRs).

@jamesmunns
Copy link
Member

bors r+

bors bot added a commit that referenced this pull request Nov 14, 2018
25: This year in embedded Rust r=jamesmunns a=japaric

This is the blog post I mentioned during the last meeting. I'd like to publish
it next Wednesday.

All kind of feedback is welcomed! Let me know if there's something you'd like to
see mentioned in this post.

Blockers for publishing this:

- [x] docs.rust-embedded.org links should be up and running. This seems good to
  go for now but has been a bit flaky. We should keep an eye on it. cc
  @rust-embedded/infrastructure

- [x] book: remove empty chapters, chapter title freeze as per
  rust-embedded/book#52, move type state under static guarantees @jamesmunns

- [x] book/getting-started: add semihosting section. @japaric

- [x] book/getting-started: add registers section. @japaric / @thejpster -- see rust-embedded/book#76

- **[postponed]** book/getting-started: add ~device /~ interrupt section but this is blocked
  on svd2rust 0.14.0 so may not happen until after the blog post. @therealprof will work on this.

- [x] book/peripherals: merge the current getting-started/registers into this
  chapter. @jamesmunns / @thejpster -- see rust-embedded/book#76

- [x] rename new-book. @ryankurte

Additionally we might want to include these two in this post:

- **[postponed]** awesome-embedded-rust: "does this compile on stable?" community effort.

What: Make an issue with instructions (add version badge to each crate in the
list?) and link to it from the blog post.

I suggested this before. @rust-embedded/resources do you want to tackle this?

- [x] wg: 2019 wishlist

What: Make an issue collecting people thoughts on what should we focus on next
year: ecosystem gaps that need to be filled, docs that need to be written,
unstable stuff that should prioritized for stabilization, language feature
requests.

@rust-embedded/all thoughts? we'll probably have the "call for 2019 blog post"
soon, in any case. Should we run an informal survey ourselves, or just watch
over the incoming blog posts?

Co-authored-by: Jorge Aparicio <[email protected]>
@bors
Copy link
Contributor

bors bot commented Nov 14, 2018

Build succeeded

@bors bors bot merged commit 788b35e into master Nov 14, 2018
@bors bors bot deleted the this-year-in-embedded-rust branch November 14, 2018 11:02
@jamesmunns
Copy link
Member

@japaric posts are up, links are added. Okay to re-enable master protection whenever you get a chance.

@japaric
Copy link
Member Author

japaric commented Nov 14, 2018

@jamesmunns Thanks! I have re-enabled branch protection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants