---
name: Suggest a change
about: Describe this issue template's purpose here.
title: 'CHANGE: <summary>'
labels: ''
assignees: ''

---

A change request is considered a (small) Request-For-Comment, and requires a concrete proposal and motivation.

## Summary

How does this affect the API / end-user? (Include API-breaking changes, value-breaking changes and API additions.)

## Details

What changes does this require internally?

## Motivation

What is the motivation for this change?

Since every change has a cost (even if just API churn or extra code size), every change must have sufficient motivation. This is arguably the most important part of the RFC.

## Alternatives

Which alternatives might be considered, and why or why not?

Add "suggest a change" issue template
Add "suggest a change" issue template