-
Notifications
You must be signed in to change notification settings - Fork 92
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
69 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,69 @@ | ||
--- | ||
simd: 'XXXX' | ||
title: Title of SIMD | ||
authors: | ||
- (fill in with names of authors) | ||
category: Standard/Meta | ||
type: Core/Networking/Interface/Meta | ||
status: Draft | ||
created: (fill me in with today's date, YYYY-MM-DD) | ||
feature: (fill in with feature tracking issues once accepted) | ||
supersedes: (optional - fill this in if the SIMD supersedes a previous SIMD) | ||
superseded-by: (optional - fill this in if the SIMD is superseded by a subsequent | ||
SIMD) | ||
extends: (optional - fill this in if the SIMD extends the design of a previous | ||
SIMD) | ||
--- | ||
|
||
## Summary | ||
|
||
A brief summary of what the feature is. | ||
|
||
## Motivation | ||
|
||
Why are we doing this? What use cases does it support? What is the expected | ||
outcome? | ||
|
||
## New Terminology | ||
|
||
Is there any new terminology introduced with this proposal? | ||
|
||
## Detailed Design | ||
|
||
Explain the feature as if it was already implemented and you're explaining it | ||
to another Solana core contributor. The generally means: | ||
|
||
- Explain the proposed change and how it works | ||
- Where the feature fits in to the runtime, core, or relevant sub-system | ||
- How this feature was/could be implemented | ||
- Interaction with other features | ||
- Edge cases | ||
|
||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", | ||
"SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this | ||
document are to be interpreted as described in [RFC | ||
2119](https://www.ietf.org/rfc/rfc2119.txt) and [RFC | ||
8174](https://www.ietf.org/rfc/rfc8174.txt). | ||
|
||
## Alternatives Considered | ||
|
||
What alternative designs were considered and what pros/cons does this feature | ||
have relative to them? | ||
|
||
## Impact | ||
|
||
How will the implemented proposal impacts dapp developers, validators, and core contributors? | ||
|
||
## Security Considerations | ||
|
||
What security implications/considerations come with implementing this feature? | ||
Are there any implementation-specific guidance or pitfalls? | ||
|
||
## Drawbacks *(Optional)* | ||
|
||
Why should we not do this? | ||
|
||
## Backwards Compatibility *(Optional)* | ||
|
||
Does the feature introduce any breaking changes? All incompatibilities and | ||
consequences should be listed. |