Different files, same size

[vexorian]

When the new file has exactly the same size as the old file, even when override is true, the new file won't be created. This brings issues when the old file somehow managed to be different and have the same size, something that happens usually when you are developing templates.

Some idea:

• Make it compare the file in case the sizes are equal? I guess Greed doesn't already do this due to performance or some other technical reason?
• Since we are already assuming the files are the same, if override is true or the regenerate button is clicked, replace it anyway, just without making a backup.
  • If the file truly is equal, it wouldn't matter.
  • If the file isn't equal, then Greed must replace, that's the reason user had override = true or used the regenerate button.

[wookayin]

How about using MD5 or SHA1 checksum?

[zen0wu]

Yes, Greed didn't do it because of performance consideration. But I guess it's OK to do this checking. Just read all the content of the file and do comparison.

[vexorian]

Since new file is already in memory and checksums need O(n) time, using hashes wouldn't really improve performance vs a file comparison.