A major API change was that asserts are imported from testing/asserts.ts
now rather than testing/mod.ts and assertEqual as renamed to
assertEquals to conform to what is most common in JavaScript.
This fixes an issue on Windows that causes build to fails when
fix_symlinks() is called concurrently with another build step.
It is also no longer necessary, since recent versions of git know how to
properly create symbolic links on checkout.
Operating systems have defined directories for cache files.
That allows them to do smart things such as leaving them out when doing a backup,
or deleting them when disk space gets low.
Also a %home%\.deno folder on windows made no sense whatsoever.
Fixes#481
Resolves#1705
This PR adds the Deno APIs as a global namespace named `Deno`. For backwards
compatibility, the ability to `import * from "deno"` is preserved. I have tried
to convert every test and internal code the references the module to use the
namespace instead, but because I didn't break compatibility I am not sure.
On the REPL, `deno` no longer exists, replaced only with `Deno` to align with
the regular runtime.
The runtime type library includes both the namespace and module. This means it
duplicates the whole type information. When we remove the functionality from the
runtime, it will be a one line change to the library generator to remove the
module definition from the type library.
I marked a `TODO` in a couple places where to remove the `"deno"` module, but
there are additional places I know I didn't mark.
- We don't look at this benchmark because it jumps around. It isn't
stable so doesn't feel trustable.
- It requires an extra request for every homepage visit. This is
excessive.
- I would gladly reintroduce it if we could store the results of the API
call into a JSON file like we do with other benchmarks.
