ID:160270
 
Question:

If I call a new/turf/ofanytype(location), it seems to delete the turf there and replace it with another one without me having to del the old turf.

Is the turf that was generated on top of really deleted, or am I racking up more memory space every time I do this?

I couldn't find anything in the DM reference or guide or forums on this, I'm sure I just don't know where to look.
You can only have one turf per tile. Internally it may not be deleted at all, just replaced. So you can safely assume it is garbage collected.

If you have multiple turfs on a single tile, only the turf placed last actually exist. The rest of the turfs don't exist, but their graphic representations are added to the underlays list of the primary turf. This gives the illusion that there are more on one tile.
In response to Android Data
Android Data wrote:

If you have multiple turfs on a single tile, only the turf placed last actually exist. The rest of the turfs don't exist, but their graphic representations are added to the underlays list of the primary turf. This gives the illusion that there are more on one tile.

Interesting stuff! That'll make some operations I was planning (with transparent floors) easier. Thanks.
In response to Geldonyetich
Note that is exclusively the Map Editor's behavior.
In response to Kaioken
Oh yes, definitely, The strange behavior of the way the turfs handle the new command is exactly why I was wondering what was up with the garbage collection. :P

Another interesting thing about this is because the turf is never removed, it never becomes a concern about whether or not their object and mob contents are passed off properly.