You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder if the game should count solution sizes for inline seq differently. Right now they don't have any solution size cost, I did this so as to not "punish" players for declaring var constants / not encourage magic numbers. But that can be abused by encoding lots of a solution into a inline sequence.
Maybe it would be better to have each inline seq item +1 to solution size? So seq foo[] = 1, 2, 3 would count +3 to solution size. On the other hand, maybe it's more fun as an exploit?
The text was updated successfully, but these errors were encountered:
I wonder if the game should count solution sizes for inline
seq
differently. Right now they don't have any solution size cost, I did this so as to not "punish" players for declaringvar
constants / not encourage magic numbers. But that can be abused by encoding lots of a solution into a inline sequence.Maybe it would be better to have each inline seq item +1 to solution size? So
seq foo[] = 1, 2, 3
would count +3 to solution size. On the other hand, maybe it's more fun as an exploit?The text was updated successfully, but these errors were encountered: