You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: contributing.md
+5-3
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@
7
7
8
8
-[Section 1: Intention of Design](#user-content-intention-of-design)
9
9
-[Section 2: The Basics](#user-content-the-basics)
10
-
-[Section 3: Adding a language](#user-content-adding-a-language)
10
+
-[Section 3: Adding an Exercise](#user-content-adding-an-exercise)
11
11
-[Section 4: Optimizations and Bug Fixes](#user-content-optimizations-and-bug-fixes)
12
12
13
13
## Intention of Design ##
@@ -25,14 +25,16 @@ This guide will walk you through how to contribute so that those two intents are
25
25
The biggest ask I have is that any code added is well tested. I would suggest that you do it Test Driven, but do not require it.
26
26
27
27
28
-
## Adding a language ##
28
+
## Adding an Exercise ##
29
29
30
30
### A Note
31
31
32
-
Remembering the intent with adding languages, I ask that you do not look at any of the current solutions. I do not want the exercise for every language to look like every other language.
32
+
Remembering the intent with adding an Exercise, I ask that you do not look at any of the current solutions. I do not want the exercise for every language to look like every other language.
33
33
34
34
Instead the goal is to use the best aspects of your language to recreate the desired behavior but having the solution be a language native solutions.
35
35
36
+
You can also read this full [guide](./new_exercises.md)
37
+
36
38
### Focus on Tests
37
39
38
40
Since the goal is expected behavior then I ask people to start by focusing on the tests. If you use the tests as a guide instead of the target code, you are in a better position for building a language native solution. This solution should be well designed.
Copy file name to clipboardexpand all lines: documentation/contrib/lang.md
+4-2
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,16 @@
1
1
<!--bl
2
2
(filemeta
3
-
(title "Adding a language"))
3
+
(title "Adding an Exercise"))
4
4
/bl-->
5
5
6
6
### A Note
7
7
8
-
Remembering the intent with adding languages, I ask that you do not look at any of the current solutions. I do not want the exercise for every language to look like every other language.
8
+
Remembering the intent with adding an Exercise, I ask that you do not look at any of the current solutions. I do not want the exercise for every language to look like every other language.
9
9
10
10
Instead the goal is to use the best aspects of your language to recreate the desired behavior but having the solution be a language native solutions.
11
11
12
+
You can also read this full [guide](./new_exercises.md)
13
+
12
14
### Focus on Tests
13
15
14
16
Since the goal is expected behavior then I ask people to start by focusing on the tests. If you use the tests as a guide instead of the target code, you are in a better position for building a language native solution. This solution should be well designed.
0 commit comments