Begin constructing an optimized russian space station.

Author: oli-obk

README.md

@@ -63,6 +63,7 @@ Name                                               | Leads
 [Parallel-rustc](working-groups/parallel-rustc/)   | [@Zoxc][Zoxc] and [@michaelwoerister][michaelwoerister]                              | Making parallel compilation the default for rustc                | February 2019 | Active       | [#t-compiler/wg-parallel-rustc][parallel-rustc_stream] | N/A                             | A-parallel-queries |
 [Profile-Guided Optimization](working-groups/pgo/) | [@michaelwoerister][michaelwoerister]                              | Implementing profile-guided optimization for rustc                | February 2019 | Active       | [#t-compiler/wg-profile-guided-optimization][pgo_stream] | N/A                             | N/A |
 [rfc-2229](working-groups/rfc-2229/) | [@blitzerr][blitzerr] and [@nikomatsakis][nikomatsakis]                             |  Make a closure capture individual fields of the variable rather than the entire composite variable           | March 2019 | Active       | [#t-compiler/wg-rfc-2229][rfc-2229-stream] | N/A                             | N/A |
+[mir-opt](working-groups/mir-opt/)                 | [@oli-obk][oli-obk]                                                                  | Write MIR optimizations and refactor the MIR to be more optimizable | March 2019 | Active       | [#t-compiler/wg-mir-opt][mir-opt-stream] | N/A                             | N/A |
 
 [nikomatsakis]: https://github.com/nikomatsakis
 [cramertj]: https://github.com/cramertj
@@ -75,6 +76,7 @@ Name                                               | Leads
 [nagisa]: https://github.com/nagisa
 [Zoxc]: https://github.com/Zoxc
 [blitzerr]: https://github.com/blitzerr
+[oli-obk]: https://github.com/oli-obk
 
 [Weekly, in Zulip]: #meeting-calendar
 [nll_stream]: https://rust-lang.zulipchat.com/#narrow/stream/122657-t-compiler.2Fwg-nll
@@ -86,7 +88,7 @@ Name                                               | Leads
 [pgo_stream]: https://rust-lang.zulipchat.com/#narrow/stream/187830-t-compiler.2Fwg-profile-guided-optimization
 [parallel-rustc_stream]: https://rust-lang.zulipchat.com/#narrow/stream/187679-t-compiler.2Fwg-parallel-rustc
 [rfc-2229-stream]: https://rust-lang.zulipchat.com/#narrow/stream/189812-t-compiler.2Fwg-rfc-2229
-
+[mir-opt-stream]: https://rust-lang.zulipchat.com/#narrow/stream/189540-t-compiler.2Fwg-mir-opt
 
 ## Procedures
 

working-groups/mir-opt/FAQ.md

@@ -0,0 +1,12 @@
+# Frequently Asked Questions (FAQ)
+
+If you have a question, feel free to file an issue or ask in the working group's Zulip stream.
+
+## Is this working group optimizing the MIR of functions or the MIR-datastructures?
+
+Yes
+
+## Why is the above answer so short?
+
+We're doing both. MIR-datastructures are mostly restructured
+where necessary to make more optimizations possible.

working-groups/mir-opt/NOTES.md

@@ -0,0 +1,24 @@
+#### *<p align="center">This page is an example template and not the actual NLL working group.</p>*
+#### *<p align="center">Feel free to break this out into a directory.</p>*
+
+# Mir Optimizations (mir-opt) Meeting Notes
+This document contains meeting notes from the mir-opt working group.
+
+## 2019-02-22: [Triage Meeting][triage20190222]
+**Written by:** [@davidtwco][davidtwco]
+
+**Purpose of meeting**: Given slow winding down of the NLL working group, discussed the ongoing
+purpose of the meeting. [@spastorino](spastorino) suggested using the time as an space for open
+discussion and office hours (as previously suggested by [@pnkfelix][pnkfelix]).
+[@pnkfelix](pnkfelix) would continue to perform weekly triage before the meeting and will leave the
+triaged issues unassigned so that interested parties can assign themselves.
+
+**Place 2.0**: Discussion turned to the ongoing Place 2.0 work being undertaken by
+[@spastorino][spastorino]. Clarifications and discussion of the feasibility of current
+implementation plan took place. Work will continue as planned.
+
+[triage20190222]: https://rust-lang.zulipchat.com/#narrow/stream/122657-t-compiler.2Fwg-nll/topic/weekly.20meeting.202019.2E02.2E20/near/158880485
+
+[davidtwco]: https://github.com/davidtwco
+[spastorino]: https://github.com/spastorino
+[pnkfelix]: https://github.com/pnkfelix

working-groups/mir-opt/README.md

@@ -0,0 +1,43 @@
+# MIR Optimizations (mir-opt) Working Group
+![working group status: active][status]
+
+This working group aims to implement MIR optimizations and do the groundwork necessary to enable
+writing MIR optimizations.
+
+- **Leads:** [@oli-obk][oli-obk]
+- **Meeting Notes:** [All](NOTES.md)
+
+[status]: https://img.shields.io/badge/status-active-brightgreen.svg?style=for-the-badge
+
+## What is the goal of this working group?
+This working group aims to accomplish the following:
+
+- Implement new MIR optimizations
+- Refactor the MIR to be more optimizeable
+
+# How can I get involved?
+If you are interested in getting involved in this working group, you should introduce yourself
+in the Zulip stream. You can be added to the GitHub and Zulip
+group for the working group if you are interested in being pinged when there are available tasks.
+
+- **Desired experience level:** Any
+- **Relevant repositories:** [`rust-lang/rust`][repo] (specifically `src/librustc_mir/transforms`)
+- **Zulip stream:** [`#t-compiler/mir-opt`][zulip] on Zulip
+
+[repo]: https://github.com/rust-lang/rust
+[zulip]: https://rust-lang.zulipchat.com/#narrow/stream/189540-t-compiler.2Fwg-mir-opt
+
+## What if I don't have much time?
+If you don't have time to contribute code, consider tagging issues in the `rust` repository so
+the team can find them.
+
+## Are there any resources so I can get up to speed?
+There are some resources available for those interested in contributing to get some background
+and context:
+
+- MIR is an intermediate representation used within the compiler. We are looking to transform
+  instances of MIR into "better" instances. You can read about the MIR in
+  the [relevant rustc-guide chapter](https://rust-lang.github.io/rustc-guide/mir/index.html).
+
+## Do I need to attend any meetings?
+We don't have any meetings yet.