I'm about to publish my first kata, but I'd like to restrict the usage of certain operators & statements. How do I do this?

It says SELECT INTO is "not allowed here". How else would I assign the SELECT result to a table? I have no idea. Any advice is appreciated.

This does not classify as an issue with the kata. This is an issue with your own code.

unsigned long long int doesn't seem to be a large enough type for one of the tests in the C translation. One of my tests overflowed or truncated, and I cannot seem to find a way around this given that the return type is fixed. Any suggestions?

I get a segmentation fault when I try to alter the 'arr' argument to change the directions. Are we expected to return a different vector?

Understandable. I suppose I should've tested it more vigorously on my system, as I got the altered result when I did several tests in a row. I will write a template that'll help me test katas on my system more readily in the future. Apologies for the inconvenience and thank you for the help!

Oh, how embarrassing. All figured out, thank you for the guidance. Please ignore me! I need to study more on stack & heap memory, I reckon...

Granted, but if the st passed is "Lagon,Lily", and my function simply processes the given arguments, how could "Elizabeth" even be a possible result of the function? As I said, it returns "Lagon" on my own system when given the exact same arguments.

Very fun kata but I feel as though there are some issues with how the mallocs and frees are being handled. My solution was flagged as having a "double free or corruption" when I hadn't used free() at all in my function.

I worked it out eventually. Felt more like a hindrance than a lesson in observation, but a lesson in observation nonetheless.

The double pointer return type seems unneeded. I have compiled my program on my own system using just an array of structs as the return type, and it passes all the initial tests. Working out how to successfully return a double pointer is just a headache. I know my program works algorithmically but it crashes no matter how I initialise and return the pointer.

The most simple answer is usually so blindingly obvious, it becomes almost invisible. A great kata that tests your observational skills more than anything else.

One of the most poorly-described katas I have encountered. 2 hours wasted, but a great lesson in anger management. May its creator burn in hell.