5 kyu
Synthesize Boolean Functions From Examples
Loading description...
Algorithms
View
Career Accelerator
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.
Thank you. I have enjoyed solving this kata.
That was a really fun kata. Thanks for letting me dig out my university knowlegde of boolean algebras from 12 years ago.
Isn't
var_count
evident fromexamples
? Is there a reason why it is provided as an extra argument?it's just for convenience
Actual tests always froze the tab and even crashed it when I submit my solution ;-(
I don't think this is supposed to happen at all.
So this happens when test fails and generated boolean expression is too big (which happens in random tests), since the whole boolean expression created by the user is dumped as the test message along with ALL the failed conditions appended to it. It's too big ;-(
Can we have smaller random test cases first that will show these, and biggest random test cases that won't show these? Then at least the browser tab wouldn't instantly crash leaving us with no output.
I think probably I'll just make the random tests fail-fast so that only one big error is displayed instead of 100. I'll also make the early random tests smaller so that you don't have to parse through a 20-variable example to figure out what went wrong
updated
Hi,
cheers
PS: 6kyu...? 'doubt that...
It's actually
6.5 kyu
if you know the simple trick ;-)even with a simple trick, the abstraction level, is clearly not 7-6 kyu
Also:
The returned object is a binary AST tree, precedence rules don't apply here.
:cough:
(but if the description is clear enough about what the task is, that part of the issue should "handle itself automatically", yes)
I would agree with 6kyu if you could brute force it.
As it is, you need too much knowledge in boolean algebra for a 6kyu.
I find it baffling that your first reaction to the kata is to write a complicated brute-force search algorithm instead of a 0th-order solution. myjinxin katas are probably all
5kyu
to you too then.I would have given this 5.5 kyu and just rounded down to 6, rationale being that it's 6 kyu implementation difficulty and 5 kyu domain knowledge
...Which should obviously make it 5, not 6...
added more details to the description and bumped up the kyu
Please don't artificially deny some rankings to be chosen by others by intentionally adjusting the estimated kata rank. That's really abusing the system. (And if you want it to be approved at a specific rank you can just ask B4B or some other PUs personally to rank it whatever you like. Not like it is any less dodgy but at least you aren't jumping hoops...) I've reverted that change.
Also @B4B if you don't agree with that ranking, then leave the kata there and wait for more ranking votes? 5 ranking votes is not that much.
because ofc, Voile knows better. For sure, yeah. Maybe you're the one who's disagreeing with others, there. So far, that's the case. So stop the crap, thx.
And that's not abusing the system? You're not consistent, here.