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.
I added random tests and improved description.
Added random tests.
Added random tests.
What I meant about description was to provide, for example, basic valid syntax:
mov register, register/value
, etc. As I said, not everyone knows how it works, and as this was meant to be an introductory kata, it should be made more clear in my opinion.I just took a different approach of going through instructions and setting an error when I found one, breaking, and returning those props, as opposed to just returning when a bad instruction is found. That's why I had problems with it declared as const (probably best not to declare it all). I thought this was about assembly, not node callbacks :D
But I guess you're right about how it should be handled, I'm not a dev, idk :P This is just a nice hobby to have aside.
Unfortunately, all the usual suspects downvoted your kata to oblivion and now it's retired =/ I hope you'll have better ideas and try creating another kata. Best of luck!
When you do not have an error, you just recive
null
, and everything is OK, you can proceed.In other case the only thing you receive is an error.
Similar to try-catch and try-to-catch.
I think I already fixed all.
I'll be greateful for help :). What should random generator actually generate?
Any count of instructions: "add", "mov", "inc" with any count of operands.
Could you please clarrify this? When I solved Simplexer I had a lot fun and didn't have problems with absense of random test generator.
While it's similar to other katas, the emphasis on proper error handling makes it slightly more unique from others, and simpler, imo. Whether it's pointless or not can be decided by people voting on it. I don't see an easier version of something much harder as an issue tbh =/
With that said, there's still some work to do on description. For example, showing what each command takes as args and what it does for those unfamiliar with assembly lang.
I'm not sure why you're setting error to
null
initially, and then expecting it to be changed to object, when it is marked as const (initialize it as {} ?)Lastly, needs random tests and more complex tests like the last one. I'll vote when these issues get fixed.
Basically, yes.
There are exceedingly few kata that do not absolutely require random tests, and this is not one of them. You really should have had random tests right at publication. At the moment, you're racking up bad ratings because you don't have them ( as well as because of other reasons ), which is a shame.
You have to write one yourself.
No random tests.
Could you provide such a generator? Are you sure every kata should have such a generator?
updated
It is much simpler then others in terms of the syntax:
only 3 instructions
,no jumps
. There is not many katas related to compilers and interpreters.compilers shouldn't provide information about error position?
This people doesn't think that it is
worthless
idea:Who told you that it is
worthless
:)?By not mentioning
Error
at all?Loading more items...