---
name: Feature request
about: Suggest a new capability, API, or platform target
title: ""
labels: enhancement
assignees: ""
---

## The problem

<!--
What are you trying to do that Perry doesn't do well today? A concrete
example of code you wish you could write, or a workflow you're stuck on,
helps far more than an abstract wishlist.
-->

## Proposed solution

<!--
What would the API / CLI flag / config field look like? A sketch is fine;
we don't need a full RFC. If you have two plausible designs, call both out.
-->

```typescript
// If relevant, what the TypeScript-side usage would look like.
```

## Alternatives considered

<!--
Other approaches you thought about and why they didn't fit. "None" is a
valid answer if you're genuinely open to suggestions.
-->

## Scope

<!--
Rough size estimate so we can triage:
- [ ] Small — CLI flag, new stdlib function, doc page
- [ ] Medium — new widget, new code-gen pass, new perry.toml field
- [ ] Large — new platform target, new backend, cross-cutting compiler change
-->

## Additional context

<!--
Links to prior art in other ecosystems (Bun, Deno, Swift, etc.), benchmarks,
related issues, anything that helps scope the idea.
-->
