* 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
32 lines
712 B
Markdown
32 lines
712 B
Markdown
---
|
|
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?
|