6 kyu
Prime Primes
152 of 485rprendergast180
Loading description...
Algorithms
View
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.
What is
n
(lower case) in the description? (JavaScript)You mean the argument? Some languages do not allow uppercase letters for variable names. In JS,
N
seems to be applicable; in other languages,n
might be applicable.Just read over it. CodeWars supports multiple languages, and sometimes this stuff happens.
If it offends you that references to other languages seep through in JS descriptions, do a couple of Haskell kata. Concepts that are different are quite often left untranslated.
I can understand your point. But someone would misunderstand the
n
is denominator?As I did :(
Try to see if the python tests are good, because I fail 10 random tests and I have checked everything and it works fine. The test fail random they don't have any coleration between them. Thanks!
There's a comment every day on codewars where someone pinky swears that their code is right and tests are wrong. They're almost all wrong.
Please include the faulty test case, otherwise this is a guessing game, one that is almost certain to lead to nothing. Either that, or it is outright dismissed without consideration.
I have started playing with this site for a week I don't want to disturbe anybody, but I saw a lot of comments about this topic and I just said it. I will check it again, but I find it strange that a code works for N = 400 and N = 800 and then it doesn't work for 600. Because if it worked for 800 means all the prime primes number I found we re good, but for 600 it s strange. Sorry for bothering you I ll try to rewrite the code and maybe rethink it. Thanks !
No bother. It needs to be reproducible in order for anyone to do anything about it, that's all.
Thanks anyway, have a great one!
Tests are good! Try harder!
98 valid solutions. I'll bite the bullet and say this is not a kata issue. Closing.
Please read and follow the Troubleshooting Guide.
Raising an
Issue
means you are 99% sure the kata has a problem, and not your code, otherwise you should raise aQuestion
. If you raise anIssue
and the problem is not with the kata, it will probably rightfully be closed without addressing your problem.Ruby translation kumited :) please review and approve ~~
Hi. Could you change the first line of initial solution code to
def prime_primes(n)
with lowern
. Uppercase throws an error:This is an intriguing kata, but the sample tests are apparently for an entirely different kata!
I fixed JS version by directly copy-pasting
@Souzooka
's translation into the Edit screen. Everything should work as intended now.(using python2) All fixed tests passed while all random tests failed. The second number "expected" is always 0 in random tests.
I tried to fix the kata by editing the reference solution's
/
operator part, but my edit removed py2 entirely... At least you won't see the broken random tests, so I'm marking this issue as resolved.Random tests added, test are now using
test.assert_equals()
.JS version is still totally wrong...
Updated the description a bit.
twoOldestAges again! The author promised to fix kata three monthes ago...
I got a completely different Kata to solve than the one in description. It requires me to solve the twoOldestAges function in Javascript...
I've seen the
twoOldestAges
three times in three katas, a crazy author...Yes I saw it before too :) and even twoOldestAges is not solvable, one test is messed up... By the way what is going on with the site I get timeouts all the time?
Sorry, this was my first kata and I didn't change the initial function the user is given (twoOldestAges was the default function I used to know the syntax). I updated the kata; it should be fixed!
Sorry!
I tried to remove the JS part, but I can't do it. The author is inactive. Anyone has the will to translate it or the rights to remove it?
couldn't remove it either... I tried to empty the differnt code parts, but the engine didn't want to republish the kata this way (note: I lost the sample tests in the operation unfortunately so I used one part of the test cases... :s )
A language version can't be deleted by anyone but the author.
Don't forget to mention that the numerator has to be less than the denominator in a prime prime