Sure, two cases, both start with a symlink `/foo/bar` to a directory `/baz/dir/` that we want to copy to `/beep/boop`:

1. When `/beep/boop` already exists copy will fail.  If `bar` were a symlink to a file instead of a directory, the code below would [delete the existing symlink](https://github.com/gruntjs/grunt-contrib-copy/pull/131/files#diff-951068604e1c942635e6a1f96a88994dR94), `/beep/boop/` before creating the new one, and pass.  Seems like behavior should be consistent either way.  I'd prefer always delete, then create.
2. When neither `/beep/` nor `/beep/boop` exist, copy will fail trying to write `boop` to the non-existant `/beep/` directory.  Again if `bar` linked to a file instead of a directory, we'd first [create `/beep/`](https://github.com/gruntjs/grunt-contrib-copy/pull/131/files#diff-951068604e1c942635e6a1f96a88994dR93) then copy in `boop`.   Should also be consistent.