> inherent to high-performance and can't be addressed. inherent? yes. > addressable? yes.
i've seen a quote somewhere, can't think where > "Complexity" seems to be a lot like "energy": you can transfer it from the > end user to one/some of the other players, but the total amount seems to > remain pretty much constant for a given task. -- Ran your first example (iterator chaining) is a great illustration. iterators rewrite the for loop they're part of for performance, they behave very unlike procs. chaining them becomes non-trivial. strformat bug: This is totally the result of complexity. Full Nim syntax, plus a DSL, in a format string? Turns out non-trivial. (the bug you highlight is because colons (part of the DSL) get removed from the substring before parsing) super annoying? yes. addressable? yes. openArray: Is 100% an inconsistency. price: complexity and corner cases like this one. (p.s. `foldl(a+b,0)` totally works) dollars not supporting refs: actually, why is this a thing?
