3 ms·

It's just a way to keep the code size in check, make sure it can be read and understood relatively easily. Don't overthink it. I doubt much, if any, research we

by torlok 2y ago

It's just a way to keep the code size in check, make sure it can be read and understood relatively easily. Don't overthink it. I doubt much, if any, research went into picking the limit. The line width is over 120 in many places, and the code inevitably ends up looking like cache_key = (device, st, dtype, op, arg, tuple(ref(x) for x in srcs)) if base is None else (st, ref(base))

kthxb 2y ago
Seems the code sample contradicts your first statement
- torlok 2y ago
  Indeed, I was making a point.
- Lerc 2y ago
  I think this might be an example of https://en.m.wikipedia.org/wiki/Goodhart's_law https://en.m.wikipedia.org/wiki/Goodhart's_law The line count probably does still act as a limit on complexity overall but perhaps less than hoped for.
kveykva 2y ago
This is truly depressing because the aspirations of tinygrad are so appealing in terms of being concise, effective and maintainable. Then, instead, they throw comprehensibility entirely out of the window.