cranelift/.github/ISSUE_TEMPLATE/improvement.md

---
name: Improvement
about: A feature request or code improvement.
title: ''
labels: ''
assignees: ''

---

Thanks for filing a feature request! Please fill out the TODOs below.

#### Feature

TODO: Brief description of the feature/improvement you'd like to see in
Cranelift/Wasmtime.

#### Benefit

TODO: What is the value of adding this in Cranelift/Wasmtime? What problems does
it solve?

#### Implementation

TODO: Do you have an implementation plan, and/or ideas for data structures or
algorithms to use?

#### Alternatives

TODO: What are the alternative implementation approaches or alternative ways to
solve the problem that this feature would solve? How do these alternatives
compare to this proposal?
[contribution] Add Github issue templates; 5 years ago			`---`
Update issue templates - Include the `cranelift` label for Cranelift bug reports - Add a Wasmtime bug report template 5 years ago			`name: Improvement`
			`about: A feature request or code improvement.`
			`title: ''`
			`labels: ''`
			`assignees: ''`

[contribution] Add Github issue templates; 5 years ago			`---`

Clean up our github issue templates * Don't use HTML comments, as they are noisy, which makes the templates more intimidating. * Use "TODO" to clearly demarcate everywhere the issue reporter should fill in some information. * Use headers and white space abundantly, which makes it easier to visually process the template and its sections at a glance, and less of an intimidating wall of text. Fixes #2661 4 years ago			`Thanks for filing a feature request! Please fill out the TODOs below.`
Improve issue template: make questions invisible, add headings, add space for writing (#1349) 5 years ago
			`#### Feature`

Clean up our github issue templates * Don't use HTML comments, as they are noisy, which makes the templates more intimidating. * Use "TODO" to clearly demarcate everywhere the issue reporter should fill in some information. * Use headers and white space abundantly, which makes it easier to visually process the template and its sections at a glance, and less of an intimidating wall of text. Fixes #2661 4 years ago			`TODO: Brief description of the feature/improvement you'd like to see in`
			`Cranelift/Wasmtime.`
Improve issue template: make questions invisible, add headings, add space for writing (#1349) 5 years ago
			`#### Benefit`

Clean up our github issue templates * Don't use HTML comments, as they are noisy, which makes the templates more intimidating. * Use "TODO" to clearly demarcate everywhere the issue reporter should fill in some information. * Use headers and white space abundantly, which makes it easier to visually process the template and its sections at a glance, and less of an intimidating wall of text. Fixes #2661 4 years ago			`TODO: What is the value of adding this in Cranelift/Wasmtime? What problems does`
			`it solve?`
Improve issue template: make questions invisible, add headings, add space for writing (#1349) 5 years ago
			`#### Implementation`

Clean up our github issue templates * Don't use HTML comments, as they are noisy, which makes the templates more intimidating. * Use "TODO" to clearly demarcate everywhere the issue reporter should fill in some information. * Use headers and white space abundantly, which makes it easier to visually process the template and its sections at a glance, and less of an intimidating wall of text. Fixes #2661 4 years ago			`TODO: Do you have an implementation plan, and/or ideas for data structures or`
			`algorithms to use?`
Improve issue template: make questions invisible, add headings, add space for writing (#1349) 5 years ago
			`#### Alternatives`

Clean up our github issue templates * Don't use HTML comments, as they are noisy, which makes the templates more intimidating. * Use "TODO" to clearly demarcate everywhere the issue reporter should fill in some information. * Use headers and white space abundantly, which makes it easier to visually process the template and its sections at a glance, and less of an intimidating wall of text. Fixes #2661 4 years ago			`TODO: What are the alternative implementation approaches or alternative ways to`
			`solve the problem that this feature would solve? How do these alternatives`
			`compare to this proposal?`