mirror of
https://github.com/roc-lang/roc.git
synced 2025-08-03 11:52:19 +00:00
added proposed status
Signed-off-by: Anton-4 <17049058+Anton-4@users.noreply.github.com>
This commit is contained in:
parent
f89df28d3f
commit
39f012a254
1 changed files with 4 additions and 1 deletions
|
@ -1,4 +1,7 @@
|
|||
# Proposal: Abilities in Roc
|
||||
|
||||
Status: we invite you to try out abilities for beta use, and are working on resolving known limitations (see issue [#2463](https://github.com/roc-lang/roc/issues/2463)).
|
||||
|
||||
This design idea addresses a variety of problems in Roc at once. It also unlocks some very exciting benefits that I didn't expect at the outset! It's a significant addition to the language, but it also means two other language features can be removed, and numbers can get a lot simpler.
|
||||
|
||||
|
||||
|
@ -542,4 +545,4 @@ This seems to be a common exercise in statically typed languages with classes; s
|
|||
In my view, type classification is a tempting but ultimately counterproductive exercise that puts a tax on a community which grows linearly with the size of that community: once enough people start doing it, everyone becomes under pressure to do the same, lest their code look suspiciously under-classified. I don't want this to happen in Roc.
|
||||
|
||||
|
||||
Hopefully the name "abilities" will frame the feature as giving a type a new ability and nothing more. It's not about saying what the type *is*, but rather what you can do with it.
|
||||
Hopefully the name "abilities" will frame the feature as giving a type a new ability and nothing more. It's not about saying what the type *is*, but rather what you can do with it.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue