Codechange: Remove assert when trying to intersect two tile areas and… #7238
On master, it doesn't. I think it doesn't make sense the first TileArea may be empty and the second one can't be empty. I find it strange. Moreover, part of the assert and its previous line are kind of redundant.
The assert was added in r18726, where the intersection of TileAreas is used for GetProductionAroundTiles. The TileAreas of industries aren't empty. So the assert would only be triggered if the location of an industry has no tiles (that doesn't happen right now: industries have at least one tile).
Anyway, I would like to intersect TileAreas where one of them may be empty (like the area of a station when its last tile is removed).
I'm not a fan of this PR as it stands - it's just a single codechange for no clear benefit.
I'm also not sure when it could trigger either - there was already a check for 0-width TileAreas, and I don't see when a TileArea with height but not width could be used