xtofl profile - python coding challenges

44

Counter-gyahun_dash 2

Darn... it took me a while to wrap my head around the `freqs` spell, but now I can happily start 2015. It is neat how it reverses the way I think about it. More

23

LexCavalera

First-LexCavalera

Hah! Finally someone like me :). I daresay I feel relieved I'm the only one not thinking `set` when thinking of Conway's game of Life. More

10

huterD

Fill a Zero-huterD

Why bother with all these different dimension combinations? Just keep the empty one and the general one, and you're done. More

30

makoto_yamagata

First-makoto_yamagata

At first glance, this one looks really great! Certainly a zero clutter solution! At second glance, my unit tests fail on it. That's because the type of the incoming data is changed into a list of tuples. The `==` doesn't care about the type. The unittest `self.assertEqual` does. So why not be More

21

hanpari

GOL via set-hanpari 1 1

Quite a find, to represent the sparse matrix as a series of living-cell-coordinates. It matches the problem greatly! It reads like a fairy tale. Or a poem if you prefer. Am I mistaken if I say that the runtime complexity is quite big, however? Take a grid xxx x.x xxx -> the center More

34

DiZ

119-DiZ 1

`len(c)` can be replaced by just `c`. You must have lost your enter key somewhere :) More

15

xiongbiao

First-xiongbiao 1

`if len(n) != 0` can be written as `if n`. More

8

KangLee

First-KangLee

Style remark: variable names tend to start with lower case in Python code. `queue[len(queue) - 1]` can be written as `queue[-1]` `Answer += 0`... why? Your can lose clutter by reversing the condition: if queue: answer += queue[-1] `print(answer)`: is that a debugging left-over? More

15

peter_parada

First-peter_parada 1 1

Great! Dispatching separated from function! I'm just wondering why you `return` a value from each of your functions... More

11

yarkcy

First-yarkcy

Quite clear solution. Checking for the second letter is an unneeded twist; you're lucky there is no 'ROTATE' command. The `else` branch in your loop is unneeded, too, though it makes the program more robust, analogous to the ability to POP from an empty stack. In order to keep a larger interpret More

27

blabaster

First-blabaster 1

After reformatting (no runtime cost :) return sum( sum( ((0,) + l) [col:col + 3] ) for l in (((0,),) + grid)[row:row + 3]) - grid[row][col] Great find to just subtract `grid[r][c]` in the end! What is the use for `((0, ) + l)` as opposed to just ` More

6

adithya217

First-adithya217

Coming from C, this is a very clear solution. The vast number of conditions, nested loops and `continue` statements makes it hard to relate to the problem statement. Python offers [generator expressions](https://wiki.python.org/moin/Generators) to simplify this greatly. You should give them a t More

15

Eldin

First-Eldin 1

very clear, expressing the `neighbors` as a plain tuple! Alignment can make these coordinates visible at a glance: [-1, -1], [-1, 0], [-1, 1], [ 0, -1], [ 0, 1], [ 1, -1], [ 1, 0], [ 1, 1] It takes some time to understand the `tempx, tempy` expression - as dedicated and clear More

21

hanpari

First-hanpari 1 1

Smart, to work with the `scope` intermediary. Smart trick to filter for `x or y`. On the other hand, I had a hard time understanding the flow within your `for b, a in around:`. It's probably easier to understand if you introduce a new variable for the new `row, col`, like `row, col = x + a, y + b More

19

Lumy

List filter-Lumy 1

Nice and dense. You don't _have_ to make it a list, if you use the `sum(1 for w in ....)` idiom. This way you can count iterators without memory limitations. More

9

ahmedaswai

No need for Lambda -ahmedaswai 1

You know that `x.__contains__(y)` can be (and should be) written as `y in x`? More

36

nickie

Using groupby-nickie 4

I love it when solutions teach me about existing library functions! Sharp and concise, this is! More

15

xiongbiao

First-xiongbiao 1

Interesting that you would pick the second char of the command to base your decision upon. What happens when you introduce a "CUT " command...? You can omit the `len` test: if l: del l[0] More

26

dagger126

First-dagger126

Indexing the given OPERATOR_NAMES just ties your code tightly to the order the operators are defined in. Tight coupling should be avoided at all cost - at least in a program where maintainability is an issue. Also: the | operator is a 'bitwise or', not your old 'logical or' (cfr https://wiki.pyt More

10

chaz.ruhl

First-chaz.ruhl

Linear search through the if-statements can easily be replaced by a dict of functions. And returning True and False just obfuscates the meaning of the code: simply returning a predicate should do. More