trackler 2.2.1.164 → 2.2.1.165
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/lib/trackler/version.rb +1 -1
- data/tracks/c/exercises/binary-search-tree/README.md +39 -0
- data/tracks/c/exercises/bracket-push/README.md +39 -0
- data/tracks/c/exercises/crypto-square/README.md +39 -0
- data/tracks/c/exercises/diamond/README.md +39 -0
- data/tracks/c/exercises/etl/README.md +39 -0
- data/tracks/c/exercises/luhn/README.md +39 -0
- data/tracks/c/exercises/minesweeper/README.md +35 -0
- data/tracks/c/exercises/pig-latin/README.md +43 -4
- data/tracks/c/exercises/prime-factors/README.md +39 -0
- data/tracks/c/exercises/rna-transcription/README.md +1 -1
- data/tracks/c/exercises/run-length-encoding/README.md +39 -0
- data/tracks/c/exercises/say/README.md +39 -0
- data/tracks/c/exercises/secret-handshake/README.md +39 -0
- data/tracks/c/exercises/two-fer/README.md +39 -0
- data/tracks/c/exercises/wordy/README.md +39 -0
- data/tracks/cpp/config.json +36 -36
- data/tracks/cpp/docs/ABOUT.md +1 -1
- data/tracks/java/exercises/luhn/.meta/version +1 -0
- data/tracks/java/exercises/luhn/src/test/java/LuhnValidatorTest.java +35 -24
- data/tracks/javascript/config.json +1 -1
- data/tracks/javascript/exercises/nth-prime/example.js +5 -1
- data/tracks/javascript/exercises/nth-prime/nth-prime.spec.js +8 -0
- data/tracks/kotlin/config.json +60 -60
- data/tracks/kotlin/exercises/binary-search/.meta/version +1 -1
- data/tracks/kotlin/exercises/flatten-array/.meta/version +1 -1
- data/tracks/kotlin/exercises/isogram/.meta/version +1 -1
- data/tracks/kotlin/exercises/minesweeper/.meta/version +1 -1
- data/tracks/kotlin/exercises/nucleotide-count/.meta/version +1 -1
- data/tracks/kotlin/exercises/pig-latin/.meta/version +1 -1
- data/tracks/kotlin/exercises/prime-factors/.meta/version +1 -1
- data/tracks/kotlin/exercises/spiral-matrix/.meta/version +1 -1
- data/tracks/kotlin/exercises/word-count/.meta/version +1 -1
- data/tracks/powershell/exercises/hamming/HammingDifference.example.ps1 +12 -2
- data/tracks/powershell/exercises/hamming/HammingDifference.ps1 +1 -12
- data/tracks/python/exercises/simple-cipher/example.py +11 -15
- data/tracks/python/exercises/simple-cipher/simple_cipher.py +0 -5
- data/tracks/python/exercises/simple-cipher/simple_cipher_test.py +69 -70
- data/tracks/reasonml/bin/new-exercise.sh +11 -0
- data/tracks/reasonml/config.json +11 -0
- data/tracks/reasonml/exercises/anagram/__tests__/Anagram_test.re +44 -0
- data/tracks/reasonml/exercises/anagram/bsconfig.json +30 -0
- data/tracks/reasonml/exercises/anagram/package.json +20 -0
- data/tracks/reasonml/exercises/anagram/src/Example.re +26 -0
- data/tracks/reasonml/template/bsconfig.json +30 -0
- data/tracks/reasonml/template/package.json +20 -0
- data/tracks/reasonml/template/src/Example.re +0 -0
- metadata +11 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 0b8e0bb7fd918e45a309c83bcac2cd6947da2bcc
|
4
|
+
data.tar.gz: 1574e191fe7b26626bad390b830cad9a8d8285b2
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: bc70fec65d3b51adeb713b809d41384ad46bb6187a62312bd54bfcce5c955ccb86f6c7a685bdf682d3d12c2cf42624ef4d27e397d1861ea88ab7fa60c088e5a7
|
7
|
+
data.tar.gz: 32dd8cd336a2f9bfee62493d11f09b15f33847f7e9f3a7cd4496fb2fc00a91cb7bc0567d8a7e2b32f96387b631c2a4adc6dac5ba538596e4a69d774ee9d9fd52
|
data/lib/trackler/version.rb
CHANGED
@@ -1,3 +1,5 @@
|
|
1
|
+
# Binary Search Tree
|
2
|
+
|
1
3
|
Insert and search for numbers in a binary tree.
|
2
4
|
|
3
5
|
When we need to represent sorted data, an array does not make a good
|
@@ -51,3 +53,40 @@ And if we then added 1, 5, and 7, it would look like this
|
|
51
53
|
/ \ / \
|
52
54
|
1 3 5 7
|
53
55
|
|
56
|
+
## Getting Started
|
57
|
+
|
58
|
+
Make sure you have read the
|
59
|
+
[C page](http://exercism.io/languages/c) on the Exercism site. This covers
|
60
|
+
the basic information on setting up the development environment expected
|
61
|
+
by the exercises.
|
62
|
+
|
63
|
+
|
64
|
+
## Passing the Tests
|
65
|
+
|
66
|
+
Get the first test compiling, linking and passing by following the [three
|
67
|
+
rules of test-driven development][3-tdd-rules].
|
68
|
+
|
69
|
+
The included makefile can be used to create and run the tests using the `test`
|
70
|
+
task.
|
71
|
+
|
72
|
+
make test
|
73
|
+
|
74
|
+
Create just the functions you need to satisfy any compiler errors and get the
|
75
|
+
test to fail. Then write just enough code to get the test to pass. Once you've
|
76
|
+
done that, move onto the next test.
|
77
|
+
|
78
|
+
[3-tdd-rules]: http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd
|
79
|
+
|
80
|
+
As you progress through the tests, take the time to refactor your
|
81
|
+
implementation for readability and expressiveness and then go on to the next
|
82
|
+
test.
|
83
|
+
|
84
|
+
Try to use standard C99 facilities in preference to writing your own
|
85
|
+
low-level algorithms or facilities by hand.
|
86
|
+
|
87
|
+
## Source
|
88
|
+
|
89
|
+
Josh Cheek [https://twitter.com/josh_cheek](https://twitter.com/josh_cheek)
|
90
|
+
|
91
|
+
## Submitting Incomplete Solutions
|
92
|
+
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|
@@ -1,3 +1,42 @@
|
|
1
|
+
# Bracket Push
|
2
|
+
|
1
3
|
Given a string containing brackets `[]`, braces `{}` and parentheses `()`,
|
2
4
|
verify that all the pairs are matched and nested correctly.
|
3
5
|
|
6
|
+
## Getting Started
|
7
|
+
|
8
|
+
Make sure you have read the
|
9
|
+
[C page](http://exercism.io/languages/c) on the Exercism site. This covers
|
10
|
+
the basic information on setting up the development environment expected
|
11
|
+
by the exercises.
|
12
|
+
|
13
|
+
|
14
|
+
## Passing the Tests
|
15
|
+
|
16
|
+
Get the first test compiling, linking and passing by following the [three
|
17
|
+
rules of test-driven development][3-tdd-rules].
|
18
|
+
|
19
|
+
The included makefile can be used to create and run the tests using the `test`
|
20
|
+
task.
|
21
|
+
|
22
|
+
make test
|
23
|
+
|
24
|
+
Create just the functions you need to satisfy any compiler errors and get the
|
25
|
+
test to fail. Then write just enough code to get the test to pass. Once you've
|
26
|
+
done that, move onto the next test.
|
27
|
+
|
28
|
+
[3-tdd-rules]: http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd
|
29
|
+
|
30
|
+
As you progress through the tests, take the time to refactor your
|
31
|
+
implementation for readability and expressiveness and then go on to the next
|
32
|
+
test.
|
33
|
+
|
34
|
+
Try to use standard C99 facilities in preference to writing your own
|
35
|
+
low-level algorithms or facilities by hand.
|
36
|
+
|
37
|
+
## Source
|
38
|
+
|
39
|
+
Ginna Baker
|
40
|
+
|
41
|
+
## Submitting Incomplete Solutions
|
42
|
+
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|
@@ -1,3 +1,5 @@
|
|
1
|
+
# Crypto Square
|
2
|
+
|
1
3
|
Implement the classic method for composing secret messages called a square code.
|
2
4
|
|
3
5
|
Given an English text, output the encoded version of that text.
|
@@ -67,3 +69,40 @@ aohghn
|
|
67
69
|
sseoau
|
68
70
|
```
|
69
71
|
|
72
|
+
## Getting Started
|
73
|
+
|
74
|
+
Make sure you have read the
|
75
|
+
[C page](http://exercism.io/languages/c) on the Exercism site. This covers
|
76
|
+
the basic information on setting up the development environment expected
|
77
|
+
by the exercises.
|
78
|
+
|
79
|
+
|
80
|
+
## Passing the Tests
|
81
|
+
|
82
|
+
Get the first test compiling, linking and passing by following the [three
|
83
|
+
rules of test-driven development][3-tdd-rules].
|
84
|
+
|
85
|
+
The included makefile can be used to create and run the tests using the `test`
|
86
|
+
task.
|
87
|
+
|
88
|
+
make test
|
89
|
+
|
90
|
+
Create just the functions you need to satisfy any compiler errors and get the
|
91
|
+
test to fail. Then write just enough code to get the test to pass. Once you've
|
92
|
+
done that, move onto the next test.
|
93
|
+
|
94
|
+
[3-tdd-rules]: http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd
|
95
|
+
|
96
|
+
As you progress through the tests, take the time to refactor your
|
97
|
+
implementation for readability and expressiveness and then go on to the next
|
98
|
+
test.
|
99
|
+
|
100
|
+
Try to use standard C99 facilities in preference to writing your own
|
101
|
+
low-level algorithms or facilities by hand.
|
102
|
+
|
103
|
+
## Source
|
104
|
+
|
105
|
+
J Dalbey's Programming Practice problems [http://users.csc.calpoly.edu/~jdalbey/103/Projects/ProgrammingPractice.html](http://users.csc.calpoly.edu/~jdalbey/103/Projects/ProgrammingPractice.html)
|
106
|
+
|
107
|
+
## Submitting Incomplete Solutions
|
108
|
+
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|
@@ -1,3 +1,5 @@
|
|
1
|
+
# Diamond
|
2
|
+
|
1
3
|
The diamond kata takes as its input a letter, and outputs it in a diamond
|
2
4
|
shape. Given a letter, it prints a diamond starting with 'A', with the
|
3
5
|
supplied letter at the widest point.
|
@@ -50,3 +52,40 @@ E·······E
|
|
50
52
|
····A····
|
51
53
|
```
|
52
54
|
|
55
|
+
## Getting Started
|
56
|
+
|
57
|
+
Make sure you have read the
|
58
|
+
[C page](http://exercism.io/languages/c) on the Exercism site. This covers
|
59
|
+
the basic information on setting up the development environment expected
|
60
|
+
by the exercises.
|
61
|
+
|
62
|
+
|
63
|
+
## Passing the Tests
|
64
|
+
|
65
|
+
Get the first test compiling, linking and passing by following the [three
|
66
|
+
rules of test-driven development][3-tdd-rules].
|
67
|
+
|
68
|
+
The included makefile can be used to create and run the tests using the `test`
|
69
|
+
task.
|
70
|
+
|
71
|
+
make test
|
72
|
+
|
73
|
+
Create just the functions you need to satisfy any compiler errors and get the
|
74
|
+
test to fail. Then write just enough code to get the test to pass. Once you've
|
75
|
+
done that, move onto the next test.
|
76
|
+
|
77
|
+
[3-tdd-rules]: http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd
|
78
|
+
|
79
|
+
As you progress through the tests, take the time to refactor your
|
80
|
+
implementation for readability and expressiveness and then go on to the next
|
81
|
+
test.
|
82
|
+
|
83
|
+
Try to use standard C99 facilities in preference to writing your own
|
84
|
+
low-level algorithms or facilities by hand.
|
85
|
+
|
86
|
+
## Source
|
87
|
+
|
88
|
+
Seb Rose [http://claysnow.co.uk/recycling-tests-in-tdd/](http://claysnow.co.uk/recycling-tests-in-tdd/)
|
89
|
+
|
90
|
+
## Submitting Incomplete Solutions
|
91
|
+
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|
@@ -1,3 +1,5 @@
|
|
1
|
+
# ETL
|
2
|
+
|
1
3
|
We are going to do the `Transform` step of an Extract-Transform-Load.
|
2
4
|
|
3
5
|
### ETL
|
@@ -44,3 +46,40 @@ variety of languages, each with its own unique scoring table. For
|
|
44
46
|
example, an "E" is scored at 2 in the Māori-language version of the
|
45
47
|
game while being scored at 4 in the Hawaiian-language version.
|
46
48
|
|
49
|
+
## Getting Started
|
50
|
+
|
51
|
+
Make sure you have read the
|
52
|
+
[C page](http://exercism.io/languages/c) on the Exercism site. This covers
|
53
|
+
the basic information on setting up the development environment expected
|
54
|
+
by the exercises.
|
55
|
+
|
56
|
+
|
57
|
+
## Passing the Tests
|
58
|
+
|
59
|
+
Get the first test compiling, linking and passing by following the [three
|
60
|
+
rules of test-driven development][3-tdd-rules].
|
61
|
+
|
62
|
+
The included makefile can be used to create and run the tests using the `test`
|
63
|
+
task.
|
64
|
+
|
65
|
+
make test
|
66
|
+
|
67
|
+
Create just the functions you need to satisfy any compiler errors and get the
|
68
|
+
test to fail. Then write just enough code to get the test to pass. Once you've
|
69
|
+
done that, move onto the next test.
|
70
|
+
|
71
|
+
[3-tdd-rules]: http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd
|
72
|
+
|
73
|
+
As you progress through the tests, take the time to refactor your
|
74
|
+
implementation for readability and expressiveness and then go on to the next
|
75
|
+
test.
|
76
|
+
|
77
|
+
Try to use standard C99 facilities in preference to writing your own
|
78
|
+
low-level algorithms or facilities by hand.
|
79
|
+
|
80
|
+
## Source
|
81
|
+
|
82
|
+
The Jumpstart Lab team [http://jumpstartlab.com](http://jumpstartlab.com)
|
83
|
+
|
84
|
+
## Submitting Incomplete Solutions
|
85
|
+
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|
@@ -1,3 +1,5 @@
|
|
1
|
+
# Luhn
|
2
|
+
|
1
3
|
Given a number determine whether or not it is valid per the Luhn formula.
|
2
4
|
|
3
5
|
The [Luhn algorithm](https://en.wikipedia.org/wiki/Luhn_algorithm) is
|
@@ -62,3 +64,40 @@ Sum the digits
|
|
62
64
|
|
63
65
|
57 is not evenly divisible by 10, so this number is not valid.
|
64
66
|
|
67
|
+
## Getting Started
|
68
|
+
|
69
|
+
Make sure you have read the
|
70
|
+
[C page](http://exercism.io/languages/c) on the Exercism site. This covers
|
71
|
+
the basic information on setting up the development environment expected
|
72
|
+
by the exercises.
|
73
|
+
|
74
|
+
|
75
|
+
## Passing the Tests
|
76
|
+
|
77
|
+
Get the first test compiling, linking and passing by following the [three
|
78
|
+
rules of test-driven development][3-tdd-rules].
|
79
|
+
|
80
|
+
The included makefile can be used to create and run the tests using the `test`
|
81
|
+
task.
|
82
|
+
|
83
|
+
make test
|
84
|
+
|
85
|
+
Create just the functions you need to satisfy any compiler errors and get the
|
86
|
+
test to fail. Then write just enough code to get the test to pass. Once you've
|
87
|
+
done that, move onto the next test.
|
88
|
+
|
89
|
+
[3-tdd-rules]: http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd
|
90
|
+
|
91
|
+
As you progress through the tests, take the time to refactor your
|
92
|
+
implementation for readability and expressiveness and then go on to the next
|
93
|
+
test.
|
94
|
+
|
95
|
+
Try to use standard C99 facilities in preference to writing your own
|
96
|
+
low-level algorithms or facilities by hand.
|
97
|
+
|
98
|
+
## Source
|
99
|
+
|
100
|
+
The Luhn Algorithm on Wikipedia [http://en.wikipedia.org/wiki/Luhn_algorithm](http://en.wikipedia.org/wiki/Luhn_algorithm)
|
101
|
+
|
102
|
+
## Submitting Incomplete Solutions
|
103
|
+
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|
@@ -1,3 +1,5 @@
|
|
1
|
+
# Minesweeper
|
2
|
+
|
1
3
|
Add the numbers to a minesweeper board.
|
2
4
|
|
3
5
|
Minesweeper is a popular game where the user has to find the mines using
|
@@ -24,3 +26,36 @@ into this:
|
|
24
26
|
| 111 |
|
25
27
|
+-----+
|
26
28
|
|
29
|
+
## Getting Started
|
30
|
+
|
31
|
+
Make sure you have read the
|
32
|
+
[C page](http://exercism.io/languages/c) on the Exercism site. This covers
|
33
|
+
the basic information on setting up the development environment expected
|
34
|
+
by the exercises.
|
35
|
+
|
36
|
+
|
37
|
+
## Passing the Tests
|
38
|
+
|
39
|
+
Get the first test compiling, linking and passing by following the [three
|
40
|
+
rules of test-driven development][3-tdd-rules].
|
41
|
+
|
42
|
+
The included makefile can be used to create and run the tests using the `test`
|
43
|
+
task.
|
44
|
+
|
45
|
+
make test
|
46
|
+
|
47
|
+
Create just the functions you need to satisfy any compiler errors and get the
|
48
|
+
test to fail. Then write just enough code to get the test to pass. Once you've
|
49
|
+
done that, move onto the next test.
|
50
|
+
|
51
|
+
[3-tdd-rules]: http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd
|
52
|
+
|
53
|
+
As you progress through the tests, take the time to refactor your
|
54
|
+
implementation for readability and expressiveness and then go on to the next
|
55
|
+
test.
|
56
|
+
|
57
|
+
Try to use standard C99 facilities in preference to writing your own
|
58
|
+
low-level algorithms or facilities by hand.
|
59
|
+
|
60
|
+
## Submitting Incomplete Solutions
|
61
|
+
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|
@@ -1,3 +1,5 @@
|
|
1
|
+
# Pig Latin
|
2
|
+
|
1
3
|
Implement a program that translates from English to Pig Latin.
|
2
4
|
|
3
5
|
Pig Latin is a made-up children's language that's intended to be
|
@@ -5,13 +7,50 @@ confusing. It obeys a few simple rules (below), but when it's spoken
|
|
5
7
|
quickly it's really difficult for non-children (and non-native speakers)
|
6
8
|
to understand.
|
7
9
|
|
8
|
-
- **Rule 1**: If a word begins with a vowel sound, add an "ay" sound to
|
9
|
-
|
10
|
-
- **Rule
|
11
|
-
|
10
|
+
- **Rule 1**: If a word begins with a vowel sound, add an "ay" sound to
|
11
|
+
the end of the word.
|
12
|
+
- **Rule 2**: If a word begins with a consonant sound, move it to the
|
13
|
+
end of the word, and then add an "ay" sound to the end of the word.
|
12
14
|
|
13
15
|
There are a few more rules for edge cases, and there are regional
|
14
16
|
variants too.
|
15
17
|
|
16
18
|
See <http://en.wikipedia.org/wiki/Pig_latin> for more details.
|
17
19
|
|
20
|
+
## Getting Started
|
21
|
+
|
22
|
+
Make sure you have read the
|
23
|
+
[C page](http://exercism.io/languages/c) on the Exercism site. This covers
|
24
|
+
the basic information on setting up the development environment expected
|
25
|
+
by the exercises.
|
26
|
+
|
27
|
+
|
28
|
+
## Passing the Tests
|
29
|
+
|
30
|
+
Get the first test compiling, linking and passing by following the [three
|
31
|
+
rules of test-driven development][3-tdd-rules].
|
32
|
+
|
33
|
+
The included makefile can be used to create and run the tests using the `test`
|
34
|
+
task.
|
35
|
+
|
36
|
+
make test
|
37
|
+
|
38
|
+
Create just the functions you need to satisfy any compiler errors and get the
|
39
|
+
test to fail. Then write just enough code to get the test to pass. Once you've
|
40
|
+
done that, move onto the next test.
|
41
|
+
|
42
|
+
[3-tdd-rules]: http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd
|
43
|
+
|
44
|
+
As you progress through the tests, take the time to refactor your
|
45
|
+
implementation for readability and expressiveness and then go on to the next
|
46
|
+
test.
|
47
|
+
|
48
|
+
Try to use standard C99 facilities in preference to writing your own
|
49
|
+
low-level algorithms or facilities by hand.
|
50
|
+
|
51
|
+
## Source
|
52
|
+
|
53
|
+
The Pig Latin exercise at Test First Teaching by Ultrasaurus [https://github.com/ultrasaurus/test-first-teaching/blob/master/learn_ruby/pig_latin/](https://github.com/ultrasaurus/test-first-teaching/blob/master/learn_ruby/pig_latin/)
|
54
|
+
|
55
|
+
## Submitting Incomplete Solutions
|
56
|
+
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|
@@ -1,3 +1,5 @@
|
|
1
|
+
# Prime Factors
|
2
|
+
|
1
3
|
Compute the prime factors of a given natural number.
|
2
4
|
|
3
5
|
A prime number is only evenly divisible by itself and 1.
|
@@ -27,3 +29,40 @@ You can check this yourself:
|
|
27
29
|
- = 60
|
28
30
|
- Success!
|
29
31
|
|
32
|
+
## Getting Started
|
33
|
+
|
34
|
+
Make sure you have read the
|
35
|
+
[C page](http://exercism.io/languages/c) on the Exercism site. This covers
|
36
|
+
the basic information on setting up the development environment expected
|
37
|
+
by the exercises.
|
38
|
+
|
39
|
+
|
40
|
+
## Passing the Tests
|
41
|
+
|
42
|
+
Get the first test compiling, linking and passing by following the [three
|
43
|
+
rules of test-driven development][3-tdd-rules].
|
44
|
+
|
45
|
+
The included makefile can be used to create and run the tests using the `test`
|
46
|
+
task.
|
47
|
+
|
48
|
+
make test
|
49
|
+
|
50
|
+
Create just the functions you need to satisfy any compiler errors and get the
|
51
|
+
test to fail. Then write just enough code to get the test to pass. Once you've
|
52
|
+
done that, move onto the next test.
|
53
|
+
|
54
|
+
[3-tdd-rules]: http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd
|
55
|
+
|
56
|
+
As you progress through the tests, take the time to refactor your
|
57
|
+
implementation for readability and expressiveness and then go on to the next
|
58
|
+
test.
|
59
|
+
|
60
|
+
Try to use standard C99 facilities in preference to writing your own
|
61
|
+
low-level algorithms or facilities by hand.
|
62
|
+
|
63
|
+
## Source
|
64
|
+
|
65
|
+
The Prime Factors Kata by Uncle Bob [http://butunclebob.com/ArticleS.UncleBob.ThePrimeFactorsKata](http://butunclebob.com/ArticleS.UncleBob.ThePrimeFactorsKata)
|
66
|
+
|
67
|
+
## Submitting Incomplete Solutions
|
68
|
+
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|