Skip to content

Commit 370c187

Browse files
authored
Withdraw RFC 43 (gencap-write) (#238)
1 parent 65dad63 commit 370c187

2 files changed

Lines changed: 45 additions & 0 deletions

File tree

text/0043-gencap-write.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,11 @@
33
- RFC PR: https://github.com/ponylang/rfcs/pull/93
44
- Pony Issue: https://github.com/ponylang/ponyc/issues/2060
55

6+
# Status
7+
8+
Withdrawn 2026-09-03 by [RFC 238](0238-withdraw-gencap-write.md).
9+
The text below remains as a historical record and does not describe accepted Pony behavior.
10+
611
# Summary
712

813
Add `#write`, a new gencap for use in type parameter constraints, implying the capability set: `{iso, trn, ref}`.

text/0238-withdraw-gencap-write.md

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
- Feature Name: withdraw-gencap-write
2+
- Start Date: 2026-09-03
3+
- RFC PR: https://github.com/ponylang/rfcs/pull/238
4+
- Pony Issue: https://github.com/ponylang/ponyc/issues/2060
5+
6+
# Summary
7+
8+
Withdraw RFC 43, "gencap-write". The original RFC stays in the repository as a historical record but is no longer an accepted proposal.
9+
10+
# Motivation
11+
12+
RFC 43 was accepted in 2017 and has never been implemented. The original author has since recommended against pursuing the feature, noting that the gencap didn't solve their problem and that the subtle edge cases in generic subtyping make adding new generic caps risky.
13+
14+
No one has needed this feature in the nine years since it was accepted. Leaving it on the accepted list implies the feature is wanted and would be merged if implemented, neither of which is true.
15+
16+
# Detailed design
17+
18+
Add a note to the top of `text/0043-gencap-write.md` recording that the RFC has been withdrawn and pointing to this RFC.
19+
20+
Close ponyc issue #2060 with a comment pointing at this RFC.
21+
22+
# How We Teach This
23+
24+
Nothing to teach. RFC 43 was never implemented and no user code depends on it.
25+
26+
# How We Test This
27+
28+
Nothing to test. No code changes are involved.
29+
30+
# Drawbacks
31+
32+
None. RFC 43 was never implemented and no work is in progress against it.
33+
34+
# Alternatives
35+
36+
Leave RFC 43 on the accepted list. This keeps an "accepted" RFC that no one wants implemented and whose author recommends against it.
37+
38+
# Unresolved questions
39+
40+
None.

0 commit comments

Comments
 (0)