---
# System prepended metadata

title: Draft

---

# Draft 

## Ideas

* gccrs is a thing
* while the Rust Project does not necessarily endorse gccrs, it's a serious project and we want to cooperate
* people from both projects have had good productive conversations
  * we're working together regularly and are cooperating
* the Rust Project appreciates the steps we are taking to ensure gccrs does not harm the Rust ecosystem, as the goal is to improve it in any way we can and not hurt it.
  * list those steps
  * show big error message
  * list more collaboration efforts like wanting to contribute to the spec
* things that are not expected to match and are non-features
* what the ecosystem can expect
  * a crate should not change to allow compilation by gccrs
  * gccrs will reuse the same standard libraries as rustc
    * not the same APIs, the same *libraries*, taken directly from rustc's repository
  * the goal of gccrs is not to add new features to the Rust language and bypass the RFC process
* what the future looks like
* looking forward to more collaboration in the future!

## Ideas - organized into sections

* Introduction
  * What is gccrs?
  * Why?
  * Why this blogpost?
* Cooperation efforts
  * Talking with members of the Rust project
  * Productive conversations with people from multiple Rust teams
  * Lots of help from influential Rust figures (name them?)
  * We want to give back, for example on the spec effort
    * Detail how gccrs *may* help and wants to help
  * We want to help more people benefit from the efforts of Rust-for-Linux
  * GCC analyzer on Rust code
    * Help with unsafe Rust code
    * Help with interacting with C APIs
  * Big error message
* What Rust users should expect from gccrs
  * No changes should be required for libraries to compile using gccrs
  * gccrs will reuse the same Rust standard libraries
    * Not the same APIs, the same libraries taken directly from the compiler.
  * The goal of gccrs is not to add new features to the Rust language and bypass the RFC process
* What the future looks like
  * Passing the rustc testsuite
  * Borrow checking with polonius
    * Contributing to polonius where we can
  * Maybe more integrations with more formalization efforts of the Rust programming language, such as Chalk
  * More collaboration!
  * gccrs will be at EuroRust in Brussels and wants to meet all of you
