Reorg

We’ve been adding code without much thought to the overall directory structure. I suggest the following renames:

//net/http.ts -> //http/mod.ts
//net/file_server.ts -> //http/file_server.ts

//net/bufio.ts -> //io/bufio.ts

//net/textproto.ts -> //textproto/mod.ts

//path/index.ts -> //fs/path.ts
//mkdirp/index.ts -> //fs/mkdirp.ts

//logging/index.ts -> //log/mod.ts

//flags/index.ts -> //flags/mod.ts

//colors/index.ts -> //colors/mod.ts

Along with the associated tests.

If you’re worried about breaking existing code:

1. People should link to tagged releases of deno_std … EG “https://deno.land/x/std@v0.2.4/net/http.ts” … we do not make stability guarantees for master.
2. It’s better to make these changes now, when deno_std is young than later.

[ry]

I’m maybe open to deno.land registry hacks like that but this discussion is more about the style guide for deno in general.

1. I think we all agree that index.ts is a bad idea because it comes with the wrong connotations.
2. We’d like to avoid a lot of module specifiers that look like this “/foo/bar/mod.ts” - it’s a waste of space when “/foo/bar.ts” would work.
3. We’d also like to avoid a lot of module specifiers that look like “/foo/bar/bar.ts” - also a waste of space.
4. I’m hesitant to populate the root directory of deno_std with .ts files. It seems messy.

I feel like the ideal situation would be if we figured out some top level categories like “fs” and “net” that we could organize into? E.G.

//term/colors.ts
//fs/path.ts
//net/http.ts

[ry]

@tunnckoCore I wrote about it in the style guide (README.md) of this project:

index.ts comes with the wrong connotations - and main.ts should be reserved for executable programs. The filename mod.ts follows Rust’s convention, is shorter than index.ts, and doesn’t come with any preconceived notions about how it might work.