I'm going to be starting a project (a programming challenge) where the compiled source code must be under a certain amount of bytes, and I already know that I am going to be having trouble meeting that criteria.
Therefore, I am going to have to take certain measures to reduce the size of my code that I would not normally take in normal code that wasn't a challenge.
Is this on-topic because it is reducing the code size. Or, because I will have had to take abstract measures, is it considered golfing?
The above text is very specific: more generally, my question is "What is the difference between golfing and reducing code size?".
Where does Code Review draw that line between a user that is actually looking for their code to be golfed and a user that is actually looking for their code size to be reduced.
Note that when I say "golfing", I mean golfing the compiled output: this does not mean to obfuscate and compact the textual source code itself.