Deno: Unstable standard library

[lucacasonato]

Parts of the standard library now require the --unstable option to function. I suggest we move all things that use unstable APIs into different files which are then re-exported by multiple entry points: mod.ts and unstable.ts. unstable.ts would re export mod.ts + all unstable features.

[Soremwar]

@lucacasonato I would like to take on this

[lucacasonato]

I should clarify that this is just an idea, and that @ry, @bartlomieju and @piscisaureus have to make the decision on if this is how they want to proceed or if they have other ideas in mind. I am not a maintainer so I am not the one to make decisions.

So I think you should wait until there is some feedback from them.

[githubmann]

Will be prefix of the unstable function named with UNSTATBLE_? just like react.

[jsejcksn]

This bit me today when using https://deno.land/std/permissions/mod.ts;

If they aren't relocated to separate files, then some kind of clear indication that --unstable is required for use.

[jsejcksn]

Convention is ok, but it would be better if there were a built-in mechanism for this as long as there is an unstable API—not just in the standard library, but for all modules. Currently, if a module uses the unstable API, I have no way of knowing, except to parse compilation error messages.

@lucacasonato suggested on Discord:

it would be cool if deno info could tell you

[bartlomieju]

I think there's no reason to change it now, closing.