Ad
  • Custom User Avatar

    Yes, but since I'm not in a "classic" cursus I wasn't sure whether I can use that word ^^

    The names are obviously irrelevant, because you precised how they should be interpreted. We're just arguing about standardisation and clarity here ^^ (Maybe var_1 and var_2 would actually be a fair pick, that way you make sure everyone will read the description and not just go with what they think the names should mean)

  • Custom User Avatar

    "professional programmer in training"

    A "student"? :D

    IMO, the variable names are irrelevant as long as (var_1, var_2) represent (row, column).

  • Custom User Avatar

    Well I'm a "professional programmer in training" and I always use y as the vertical axis when I'm dealing with rows, and most graphic libraries I've used do the same. But I've occasionally seen the reverse notation as well.

    I personally think the clearer solution is to replace (x, y) by (l, c) in the description. That way absolutely no one can be confused.

  • Custom User Avatar

    I'm glad you managed to solve the kata, but I'm not joking either: when talking about matrices x and y are the most commonly used variables for coordinates representation like in plotting in math. Programming is not math, though - the first axis here is not horizontal but vertical, so x generally stands for rows, and y stands for columns.

  • Custom User Avatar

    Are you even serious? A list of rows is the most common practice where (x, y) means row X, colunm Y; it is even stated in the description that (x, y) tuples should be interpreted as toll_map[x][y] positions, not as toll_map[y][x]. If it WAS a list of columns, it'd be explicitly stated like in this kata (as it's an uncommon practice to do so). Don't raise an issue if you don't understand the task/can't read the description properly.

    The simplest fix is to just transpose all direction strings in the example output and test cases which would swap y and x and confirm to the more sensible format in the clarification. I know this would break already submitted solutions but 13 is not that many and given the age of this kata all submitters are most likely still active.

    Now this is just bullshit. No one will change the kata so 13 correct solutions will fail and your incorrect one will succeed.

  • Custom User Avatar

    Just ignore this comment at the top of the trainer: it appears sometimes. Currently, all previous soluitons are still valid, so no problem on this side.

    About your solution, it's hard to tell. Are you sure your code doesn't end up in an infinite loop in some edge case? (timing is not reliable when you get a... time out... Actually, you shouldn't even get a time value... unless...)

    Unless you're actually not timing out, but rather "printing out": are you sure that the error is not "max buffer reached"? In that case, that would mean that your solution prints too much things to the console.

  • Custom User Avatar

    Thanks for the suggestion. It looks like this may have been a result of the kata not updating properly before, but it's update now.