mirror of
https://github.com/roc-lang/roc.git
synced 2024-11-11 16:51:53 +03:00
fix broken wip links
This commit is contained in:
parent
fdc00ac802
commit
c4d18be25d
@ -29,7 +29,7 @@ There are three loose stages that a design proposal can go through in Roc: idea,
|
||||
|
||||
In the idea stage, people are encouraged to describe their idea and explore the problem, potential solutions, and tradeoffs. It's a good idea to share the idea in [`#ideas` on Zulip](https://roc.zulipchat.com/#narrow/stream/304641-ideas). There's no prerequisite for sharing an idea (it's only an idea, after all!) and likewise there's also no obligation for any contributor to necessarily act on it.
|
||||
|
||||
If the idea seems promising and worth developing further (as confirmed by a Roc contributor with expertise in the relevant area—not necessarily the [BDFN](/wip/bdfn)), usually the next step is to get more specific with a written proposal that details all the necessary information about what the change would involve.
|
||||
If the idea seems promising and worth developing further (as confirmed by a Roc contributor with expertise in the relevant area—not necessarily the [BDFN](/bdfn)), usually the next step is to get more specific with a written proposal that details all the necessary information about what the change would involve.
|
||||
|
||||
A written proposal isn't always necessary (for example, it may be deemed a simple and uncontroversial enough change that we're comfortable proceeding straight to implementation), but since writing proposals can be time-consuming, it's definitely a good idea to get confirmation at the idea stage from an experienced contributor before taking the time to write one up.
|
||||
|
||||
|
@ -81,4 +81,4 @@ The next major performance improvement will be caching. Currently, `roc` always
|
||||
|
||||
In addition to being fast, Roc also aims to be a friendly programming language.
|
||||
|
||||
[What does _friendly_ mean here?](/wip/friendly)
|
||||
[What does _friendly_ mean here?](/friendly)
|
||||
|
@ -1,6 +1,6 @@
|
||||
# Friendly
|
||||
|
||||
Besides having a [friendly community](/wip/community), Roc also prioritizes being a user-friendly language. This impacts the syntax, semantics, and tools Roc ships with.
|
||||
Besides having a [friendly community](/community), Roc also prioritizes being a user-friendly language. This impacts the syntax, semantics, and tools Roc ships with.
|
||||
|
||||
## [Syntax and Formatter](#syntax) {#syntax}
|
||||
|
||||
@ -95,6 +95,6 @@ In the future, there are plans to add built-in support for [benchmarking](https:
|
||||
|
||||
## Functional
|
||||
|
||||
Besides being designed to be [fast](/wip/fast) and friendly, Roc is also a functional programming language.
|
||||
Besides being designed to be [fast](/fast) and friendly, Roc is also a functional programming language.
|
||||
|
||||
[What does _functional_ mean here?](/wip/functional)
|
||||
[What does _functional_ mean here?](/functional)
|
||||
|
@ -41,7 +41,7 @@ Let's start by getting acquainted with Roc's [_Read-Eval-Print-Loop_](https://en
|
||||
|
||||
You can use the online REPL at [roc-lang.org/repl](https://www.roc-lang.org/repl).
|
||||
|
||||
Or you can run this in a terminal: <code class="block">roc repl</code>, and if Roc is [installed](/wip/install.html), you should see this:
|
||||
Or you can run this in a terminal: <code class="block">roc repl</code>, and if Roc is [installed](/install), you should see this:
|
||||
|
||||
<pre>
|
||||
<samp>
|
||||
|
Loading…
Reference in New Issue
Block a user