Deno.symlink uses very broad permissions

[rrrnld]

I am unable to restrict the permissions on specific folders using --allow-read=... --allow-write=... when using Deno.symlnk, instead having to give it the complete read-write-access of the current user. Is there a rationale behind this? The tests seem to suggest like this is intentional (

deno/cli/tests/unit/symlink_test.ts

Lines 114 to 140 in 10e4b2e

	Deno.test(
	{ permissions: { read: true, write: ["."] } },
	async function symlinkNoFullWritePermissions() {
	await assertRejects(
	() => Deno.symlink("old", "new"),
	Deno.errors.PermissionDenied,
	);
	assertThrows(
	() => Deno.symlinkSync("old", "new"),
	Deno.errors.PermissionDenied,
	);
	},
	);
	Deno.test(
	{ permissions: { read: ["."], write: true } },
	async function symlinkNoFullReadPermissions() {
	await assertRejects(
	() => Deno.symlink("old", "new"),
	Deno.errors.PermissionDenied,
	);
	assertThrows(
	() => Deno.symlinkSync("old", "new"),
	Deno.errors.PermissionDenied,
	);
	},
	);

), but it's not obvious to me why that is.