fix bit logic operators

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,44 +1,40 @@
 ---
 name: Bug Report
-about: Create a bug report for Rust.
-labels: C-bug
+about: Create a bug report for RMC
+labels: bug
 ---
 <!--
-Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
-along with any information you feel relevant to replicating the bug.
+Please report security concerns to us on the
+[AWS vulnerability reporting](http://aws.amazon.com/security/vulnerability-reporting/) page.
 -->
 
-I tried this code:
+<!--
+Thank you for filing a bug report! 🐛
+Please provide a short summary of the issue, along with the information necessary to replicate.
+-->
 
+I tried this code:
+<!--
+If the reproducing code is small, please post it here.
+Otherwise, please attach the relevant files to this issue.
+Alternatively, post a link to the repository and branch that exposes the issue.
+-->
 ```rust
 <code>
 ```
 
-I expected to see this happen: *explanation*
-
-Instead, this happened: *explanation*
-
-### Meta
-<!--
-If you're using the stable version of the compiler, you should also check if the
-bug also exists in the beta or nightly versions.
--->
+using the following command line invocation:
 
-`rustc --version --verbose`:
 ```
-<version>
+<command>
 ```
 
-<!--
-Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
-environment. E.g. `RUST_BACKTRACE=1 cargo build`.
--->
-<details><summary>Backtrace</summary>
-<p>
+with RMC version:
 
-```
-<backtrace>
-```
+I expected to see this happen: *explanation*
 
-</p>
-</details>
+<!--
+If RMC crashed, please include a backtrace in the code block by setting
+`RUST_BACKTRACE=1` in your environment. E.g. `RUST_BACKTRACE=1 rmc ...`
+-->
+Instead, this happened: *explanation*

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,27 @@
+---
+name: Feature Request
+about: Create a feature request for RMC
+labels: 
+---
+<!--
+Please report security concerns to us on the
+[AWS vulnerability reporting](http://aws.amazon.com/security/vulnerability-reporting/) page.
+-->
+
+<!--
+Thank you for requesting an RMC feature!
+Please include the following information if it applies to your case:
+-->
+Requested feature:
+Use case:
+Link to relevant documentation (Rust reference, Nomicon, RFC):
+Is this a breaking change?
+
+Test case:
+<!--
+If the test-case is small, please post it here.
+Otherwise, please attach the relevant files to this issue.
+-->
+```rust
+<code>
+```

.github/ISSUE_TEMPLATE/performance_issue.md

@@ -0,0 +1,37 @@
+---
+name: Performance Issue
+about: Create a performance issue for RMC
+labels: bug
+---
+<!--
+Please report security concerns to us on the
+[AWS vulnerability reporting](http://aws.amazon.com/security/vulnerability-reporting/) page.
+-->
+
+<!--
+Thank you for filing a performance issue!
+Please provide a short summary of the issue, along with the information necessary to replicate.
+-->
+
+I tried this code:
+<!--
+If the reproducing code is small, please post it here.
+Otherwise, please attach the relevant files to this issue.
+Alternatively, post a link to the repository and branch that exposes the issue.
+-->
+```rust
+<code>
+```
+
+using the following command line invocation:
+
+```
+<command>
+```
+
+with RMC version:
+
+If this is a performance regression, how long did it use to take?
+Otherwise how much did you expect it to take?
+How long did it take?
+What stage appears to be the slowest (compilation, verification, code coverage)?