chore: deprecate Deno.Reader, Deno.ReaderSync, Deno.Writer, Deno.WriterSync and Deno.Closer

[iuioiua]

This change deprecates Deno.Reader, Deno.ReaderSync, Deno.Writer, Deno.WriterSync and Deno.Closer in favour of the Web Streams API. After discussing with Yoshiya, we both thought now might be the right time to deprecate these interfaces with v2 getting closer.

[crowlKats]

Ref #9795

[ry]

LGTM

[bartlomieju]

@iuioiua are there any APIs in deno_std that use these types that are not deprecated?

[iuioiua]

In std, we use a types.d.ts file which copies these IO interfaces exactly. Sub-modules that use these identical interfaces from types.d.ts and are not deprecated include:

• std/archive - feat: web streams based archive/tar std#1985 aims to migrate to the Web Streams API.
• std/log

[iuioiua]

Sidenote: IMO, having these identical types is confusing, and I think we should remove them and use Deno.* types.

[bartlomieju]

In std, we use a types.d.ts file which copies these IO interfaces exactly. Sub-modules that use these identical interfaces from types.d.ts and are not deprecated include:

• std/archive - feat: web streams based archive/tar deno_std#1985 aims to migrate to the Web Streams API.
• std/log

I spoke with @crowlKats about std/archive and it seems we could do compression side, but decompression is currently blocked 🤔 As for std/log - could we rewrite it to use Web streams APIs instead?

That said, I think these two shouldn't be a blocker for landing this deprecation

[iuioiua]

I spoke with @crowlKats about std/archive and it seems we could do compression side, but decompression is currently blocked 🤔

Yeah, I looked into it and couldn't fix the issue. See here.

As for std/log - could we rewrite it to use Web streams APIs instead?

Yep, I've already created an issue to do that here.

That said, I think these two shouldn't be a blocker for landing this deprecation

Agreed.

[mmastrac]

Landing for v1.39