6 kyu
One Line Task: What type is it?
41Lambdius
Loading description...
Regular Expressions
Restricted
Puzzles
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
Example tests should be repeated in Submit tests.
Solutions that do not pass the Example tests can now pass the Submit tests.
fixed
please check and close your issues
This is correct. If you want a different answer, you should specify it.
I gave this example as a demonstration of the non-obvious behavior of the operators available in the language
You are not addressing the actual issue. The expected results are unspecified.
I will now add a table of expected responses to the description
Examples are not specifications. A description should be complete and correct even if solvers skip reading any examples; examples should clarify, not specify. The problem with examples is they make solvers reverse engineer specs, i.e. read your ( author's ) mind. They are also not guaranteed to be complete.
The table works, though it does not need to be this big and this specific (
Boolean primitive or object => "Boolean", etc., would work ), but the header should be something like "Expected results" instead of "Examples".Closing, though I still suggest changing the table.
current votes (at 56 limit):
let's see how votes evolve on 45 limit
approved at kyu 6
44 might be a better limit if you wish to further restrict. There are 3 completely different solutions <= 44 atm
I was just thinking about this, but there were few examples of solutions in fewer characters. I will now change the limit to n <= 45