I edited the stackoverflow answer where this is listed (pending peer review) and created an edit to README to reflect the possibility of trying to unlink a non-hardlinked directory may orphan files ore entire directory trees, causing the permanent storage version of a memory leak.
Note: While I haven't tried it (Using High Sierra with the new FS doesn't let me create hardlinks properly) it should be possible to orphan files this way. Would recommend some sort of check in the code itself, however a bit red note in the README may be sufficient. Either way, important to know!
I edited the stackoverflow answer where this is listed (pending peer review) and created an edit to README to reflect the possibility of trying to unlink a non-hardlinked directory may orphan files ore entire directory trees, causing the permanent storage version of a memory leak.
https://github.com/selkhateeb/hardlink/commit/432b1de9beeb0dd92cb2fdade1dba9d56ec4098d
Note: While I haven't tried it (Using High Sierra with the new FS doesn't let me create hardlinks properly) it should be possible to orphan files this way. Would recommend some sort of check in the code itself, however a bit red note in the README may be sufficient. Either way, important to know!