5 kyu
Crossword Puzzle! (2x2)
130 of 277rowcased
Loading description...
Puzzles
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.
Pretty tricky kata to figure out.
All good except my code on this one. I've gone a bit insane solving this.
puzzle
should beconst char *const [2]
in C, since the user is not supposed to modify itfixed, thank you
This comment has been hidden.
Thanks for your feedback! I understand what you mean, but the task is fully explained in the description. If you feel that it isn't or you have more to add, I'm ready to listen. In the meantime, if you really thought it was a great problem, please consider upvoting or not voting, as "somewhat" actually brings the kata down. Cheers!
Alright, happy coding!
Updated to Very Satisfied, not only because I was unaware that 'somewhat' hurts the kata, but because you are right in that the problem description does match the test-cases, and I was just reading the description incorrectly. I was trying to be helpful, and ran my mouth before making 100% sure what I said was right.
Thanks for approaching this conversation kindly, and in good faith!
Much appreciated, and likewise thanks for helping Codewars be the best it can!
working more than 6h trying to resolve this kata, and im realy enjoyed this but i dont think i can take it for longer)
why at the 1st test the expected result is bothside [AG UG] [UG AG] and the 3th is failing with the mirrored results?
No worries, you can always come back to it later after solving a bunch of other kata.
Both
AG UG
andUG AG
can fit the puzzzle, so they work. So double-check other results to see that they actually fit the puzzle in that way.Welcome to Codewars, best of luck!
Thank you!)) made something in my code and it worked ))
great, glad you got it!
For Java, the first random test seems broken (if I understand the task correctly). For this puzzle:
puzzle = Q# __
, I get this error:Invalid solution ==> expected: <{"QI", "IF", 16}> but was: <{"IF", "QI", 16}>
.Thanks for your comment! I have made a correction in the tests, please try again.
Hmmm... I still have the same problem with the first test. For
puzzle = #T __
I getInvalid solution ==> expected: <{"TA", "ZA", 13}> but was: <{"QI", "TI", 13}>
. Looks like this test expects the reversed order (down word, across word, value) instead of (across word, down word, value).Try saving your code locally, refresh the page and click reset. Then drop your code back in and try again.
Yep, it worked. Thanks a lot!
Great, thanks for your help in getting the Java version running smoothly!
Nice kata!
Much appreciated!
Hi To understand an error in one of the attempt tests , I added a print and attempted again and the tests became all good. A new attempt permitted me to understand were my issue was, so it seems that the tests can't cover all the edge cases (for me, letter and hashtag in diagonal and a letter that is not at the same time the beginning and the end of two words) But remains a very interesting kata :)
The description is clear and the kata itself is funny and original. Thanks!
I appreciate the feedback on the description, and I'm glad you enjoyed the coding experience, cheers!
This was a tremendously fun kata to solve; my thanks to the author and contributors. Additionally: Major props for such a well documented Details section on this kata!
@Harleigh, thanks for your comment! I appreciate the recognition for putting in all the details. I'm glad you enjoyed solving it as much as I enjoyed making it; I hope you may like my other kata. Cheers
btw, you should add a sample tests where the letter and the
#
are on the same row.Done.
Pretty interesting one. But the approved rank is clearly more appropriate than the author's suggestion... ;p
In the output part, you should put all the ordering requirement in the same sentence.
cheers
Much appreciated! For me, the most interesting part of the experience was that I had the entire kata completely finished in both languages with brute force testing ready to go before I even began to consider a solution. So, I put it away for a time such that I could come back later and have the pleasure of solving my own kata. And yes, it was harder than I had expected and I was wrong about the rank.
Done, thanks.
Approved.
Thanks for your attention!
Hi,
There are some info that aren't very clear in the description (and since I know I almost always go way too far with your kata, I bet there are unworded restrictions in there too x) ). So...:
#
?Hello, thanks for the feedback. I have added two further bullet points to the description that I hope should cover these details:
:+1:
and
Why
(UG, UG)
is not a valid solution?The description states that the
words must be distinct
, as per the rules agreed upon by Alice and Bob.Seems, I still can't see that.
It's in the
Output
section. Should it be moved to theSome Notes
section? Or should I arrange things otherwise, concerning the rules?UPDATE: I have just now added words concerning this rule to the
Today's Proposition
section.Ah, I see.
Thanks.
I also had the exact same question even after scanning the kata thoroughly. So I would recommend describing it even more explictly somewhere. Besides that a well described fun kata!
Thanks for you comment, I added a line to the
Some Notes
part. Glad you enjoyed the kata!