Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
Instructions are unclear, needed to use the comments to figure out what to do
#FreeTomFoolery
bruh
This comment is hidden because it contains spoiler information about the solution
Language is python btw
Im confused what we're supposed to return in the case that get_concentration is called with a fruit that has not been added to the jar, I tried returning "None" which seems to work for 99% of cases but fails one with a key error of whatever the fruit type was, and when I tried returning 0 instead, I get an error saying the value isn't close enough to the expected
Bruh
This comment is hidden because it contains spoiler information about the solution
based
"The description of the task says
the value of the string s (which can be either" white "or" black ")
but the tests also include the letters w and b." -BitemNet
This happens for the python version of the challenge.
Reposting as an issue for the sake of visibility.
"alligator" is not case sensitive in Haskell, contrary to what the description states
Description could use a re write for clarity, it's "understandbale" sure, but a lot of people clearly arent understanding it, therefor it reasons that it should be rewritten to be more clear.
The kata itself is a fun challenge, but g964 really needs to work on description writing, it feels like everytime I do kata by them, I have to start by parsing the comments for a proper description of the kata that actually explains all the nauances of the challenge
See helloRupa's comment to understand what I mean
This should be the description of the kata, explains it a millions times better than the actual one
For the java version, when you return the wrong value for a test you're given the error: "expected: <X> but was: <Y>". The issue is that X seems to be set to the user's return value and Y is the expected result for the given test. Wouldn't it make more sense to have "expected: <Y> but was: <X>" instead?
TLDR: the variables for expected and actual seem to be opposite for what they actually are in the java error message "expected: <X> but was: <Y>".
Loading more items...