- 
                Notifications
    You must be signed in to change notification settings 
- Fork 368
RFC Template
        Christina-Young-NVIDIA edited this page Jan 24, 2023 
        ·
        3 revisions
      
    # <Name of Feature>
## TL;DR
<!-- Summarize the feature being proposed here -->
## Goal(s)
<!-- What are we trying to achieve here, what problems does this feature solve? -->
### Usecases
## Proposed APIs / UX
<!-- How would a user interact with this feature. Describe a workflow end to end that a user would go through to use a feature--> 
 
### Example Workflow
<!-- Psuedocode or similar prototype usage --> 
### Limitations
<!-- More important that what will this feature do is what can't this feature do. Clearly describe how a user can tell if a user  --> 
## Internal Implementation
### Design
<!-- How would the internals of this feature work. How does data flow through the system? What are the inputs, and what are the outputs? Is there any state management involved? --> 
### Extensions Required to Core API implementations
<!-- How would the current library need to change? --> 
#### Data Structures
<!-- Are there new data structures we need? -->
### Details specific for TorchScript Support 
### Details specific for FX support 
## Implementation Phases
### Prototype - <T-Shirt Size Estimate>
<!-- What is needed to be implemented to run experiments with this feature concept --> 
### MVP `(<TARGET RELEASE VERSION>)` <T-Shirt Size Estimate>
<!-- What is the most limited version of this feature that can be shipped in a minor release with reasonable level of code quality --> 
### Extension Phase 1 `(<TARGET RELEASE VERSION>)` <T-Shirt Size Estimate>
<!-- What would the next set of capabilities added to this feature be --> 
### Extension Phase 2 `(<TARGET RELEASE VERSION>)` <T-Shirt Size Estimate>
<!-- What would the next set of capabilities added to this feature be -->