#### Functional
###### Has the requirement for the allowed packages been respected? (Reminder for this project: (only [standard packages](https://golang.org/pkg/)
##### Try passing as arguments `"hello" standard`
```
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
_ _ _
| | | | | |
| |__ ___ | | | | ___
| _ \ / _ \ | | | | / _ \
| | | | | __ / | | | | | (_) |
|_| |_| \___| |_| |_| \___/
```
###### Does it display the string in the right template as an ASCII art representation as above?
##### Try passing as arguments `"hello world" shadow`
```
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
_| _| _ | _| _ |
_|_|_| _|_ | _| _ | _|_ | _| _ | _| _ |_| _| _ |_| _| _ |_|_|
_| _| _ |_|_|_| _| _ | _| _ | _| _ | _| _ | _| _ |_| _| _ | _|
_| _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ |
_| _| _ |_|_| _| _ | _|_ | _| _ | _|_ | _| _ | _|_ |_|
```
###### Does it display the string in the right template as an ASCII art representation as above?
##### Try passing as arguments `"nice 2 meet you" thinkertoy`
```
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
-- o
o o o |
o-o o-o o-o / o-O-o o-o o-o -o- o o o-o o o
| | | | |-' / | | | |-' |-' | | | | | | |
o o | o-o o-o o--o o o o o-o o-o o o--O o-o o--o
|
o--o
```
###### Does it display the string in the right template as an ASCII art representation as above?
##### Try passing as arguments `"you & me" standard`
```
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
___
_ _ ___ _ _ ( _ ) _ __ ___ ___
| | | | / _ \ | | | | / _ \/\ | '_ ` _ \ / _ \
| |_| | | (_) | | |_| | | (_> < | | | | | | | __ /
\__, | \___/ \__,_| \___/\/ |_| |_| |_| \___|
__ / /
|___/
```
###### Does it display the string in the right template as an ASCII art representation as above?
##### Try passing as arguments `"123" shadow`
```
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
_| _ |_| _|_ |_|
_|_| _| _ | _|
_| _ | _|_ |
_| _ | _|
_| _ |_|_|_| _|_ |_|
```
###### Does it display the string in the right template as an ASCII art representation as above?
##### Try passing as arguments `/(\") thinkertoy`
```
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
o o
o / | | \
/ o o
o | |
/ o o
o \ /
```
###### Does it display the string in the right template as an ASCII art representation as above?
##### Try passing as arguments `ABCDEFGHIJKLMNOPQRSTUVWXYZ shadow`
```
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
_|_ | _|_ |_| _|_ |_| _|_ |_| _|_ |_|_| _|_ |_|_| _|_ |_| _| _ | _|_ |_| _| _ | _| _ | _| _ | _| _ | _|_ | _|_ |_| _|_ | _|_ |_| _|_ |_| _|_ |_|_|_| _| _ | _| _ | _| _ | _| _ | _| _ | _|_ |_|_|_|
_| _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _|_ | _|_ | _|_ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ |
_|_|_|_| _|_ |_| _| _ | _| _ |_|_| _|_ |_| _| _ |_| _|_ |_|_| _| _ | _|_ | _| _ | _| _ | _| _ | _| _ | _| _ |_|_| _| _ |_| _|_ |_| _|_ | _| _ | _| _ | _| _ | _| _ | _| _ | _|
_| _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ |_| _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ | _| _ |
_| _| _ |_|_| _|_ |_| _|_ |_| _|_ |_|_| _| _ |_|_| _| _ | _|_ |_| _|_ | _| _ | _|_ |_|_| _| _ | _| _ | _|_ | _| _ |_| _| _ | _| _ |_|_| _| _ |_| _| _ | _| _ | _| _ | _|_ |_|_|_|
```
###### Does it display the string in the right template as an ASCII art representation as above?
##### Try passing as arguments `\"#$%&/()*+,-./ thinkertoy`
```
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
o o | |
| | | | -O-O- O o / \ o | o o
-O-O- o | | o / o / o o \|/ | /
| | -O-O- / /| o | | --O-- -o- o
-O-O- | | o / o o-O- / o o /|\ | o-o /
| | -O-O- O | o \ / o | o o O o
| | |
```
###### Does it display the string in the right template as an ASCII art representation as above?
##### Try passing as arguments `"It's Working" thinkertoy`
```
Refactor & Beautify & destruction commit
return early, remove else branches, reorder conditions and top-level functions, remove empty lines, remove unnecessary append(), fix typos, stop using testing package, remove dead code, fix mistakes in subjects, tests and solutions, remove disclaimers, reformat comments, simplify solutions, tests, add more instructions to subjects, remove obsolete files, etc.
Some of the reasons behind those modifications will be added to good-practices.en.md
Some of the exercises are now broken, they will have to be fixed, most of them have a "TODO:" comment.
5 years ago
o
o-O-o o | o o o
| | | | | / o
| -o- o-o o o o o-o o-o OO o-o o--o
| | \ \ / \ / | | | | \ | | | | |
o-O-o o o-o o o o-o o o o | o o o--O
|
o--o
```
###### Does it display the string in the right template as an ASCII art representation as above?
##### Try passing as arguments a random string with upper and lower case letters followed by one of the templates names (standard, shadow, thinkertoy, or other).
###### Does it display the expected string in the right template as an ASCII art representation?
##### Try passing as arguments a random string with numbers followed by one of the templates names (standard, shadow, thinkertoy, or other).
###### Does it display the expected string in the right template as an ASCII art representation?
##### Try passing as arguments a random string with special characters followed by one of the templates names (standard, shadow, thinkertoy, or other).
###### Does it display the expected string in the right template as an ASCII art representation?
##### Try passing as arguments a random string with numbers, spaces, special characters, upper and lower case letters followed by one of the templates names (standard, shadow, thinkertoy, or other).
###### Does it display the expected string in the right template as an ASCII art representation?
###### Is the file system well organized?
###### As an auditor, is this project up to every standard? If not, why are you failing the project?(Empty Work, Incomplete Work, Invalid compilation, Cheating, Crashing, Leaks)
#### General
###### +Does the project contain their own templates?
#### Basic
###### +Does the project runs quickly and effectively (Favoring of recursive, no unnecessary data requests, etc.)?
###### +Is the output of the program well structured? Does any letter seems to be out of line?
###### +Is there a test file for this code?
###### +Are the tests checking each possible case?
###### +Does the code obey the [good practices](https://public.01-edu.org/subjects/good-practices.en)?
#### Social
###### +Did you learn anything from this project?
###### +Would you recommend/nominate this program as an example for the rest of the school?
