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.

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

Initial commit of the second newsletter. Still some TODOs for @japaric #73

Merged
merged 6 commits into from
Mar 29, 2018

Conversation

jamesmunns
Copy link
Member

No description provided.

@jamesmunns
Copy link
Member Author

Closes #65

@jamesmunns
Copy link
Member Author

@japaric
Copy link
Member

japaric commented Mar 29, 2018

@jamesmunns I've thrown my summary into the PR. It still needs some editing (fix the headers, etc.). Let me know if you have comments or if anything is missing. I'll check this PR again in a few hours.

@japaric
Copy link
Member

japaric commented Mar 29, 2018

Another thing that I wanted to mention is that the linker issue we asked help for in the last newsletter already has a PR that will fix it in rust-lang/rust#49316.


We don't only want to make embedded Rust possible on stable; we also want to make sure the embedded targets don't regress. So we are going to add tests to rust-lang/rust CI to make sure regression block PRs from landing.

That effectively will make some of the embedded targets into the tier 1 platform. The core team is fine with adding the `thumb*` targets (ARM Cortex-M) to tier 1. Less maintained, still in development and not fully mature targets like AVR, MSP430 and RISCV will become tier 3 -- they'll be tested but won't block PRs and rust-std binaries will be produced but it's not guaranteed there will be binaries available for all nightly / beta / stable releases.
Copy link
Member Author

Choose a reason for hiding this comment

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

@japaric should AVR/MSP/RISCV be tier 2 and not tier 3?

Copy link
Member

Choose a reason for hiding this comment

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

Now that I'm actually reading the description in the Rust Platform Support page yes; it sounds like those should be called tier 2 targets.

Copy link
Member

@japaric japaric left a comment

Choose a reason for hiding this comment

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

LGTM

@japaric
Copy link
Member

japaric commented Mar 29, 2018

Thanks @jamesmunns!

@japaric japaric merged commit 2c66d1d into master Mar 29, 2018
@japaric japaric deleted the newsletter-2 branch March 29, 2018 16:24
Copy link
Member

@Emilgardis Emilgardis left a comment

Choose a reason for hiding this comment

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

oops forgot to push this

#![no_std]
extern crate core;

// but this doesn't #![feature(compiler_builtins_lib)]
Copy link
Member

Choose a reason for hiding this comment

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

This sentence could be wierd to read if you don't know about compiler-builtins

extern crate compiler_builtins;
```

In the future we might want to merge `compiler-builtins` into `core` but that requires more effort and can still be done if we do the `#![no_std]` prelude approach right now.
Copy link
Member

Choose a reason for hiding this comment

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

and can still be done later if we do

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.

3 participants