Tracking issue for `Sable.` API's

[Im-Beast]

Currently planned API's:

this list should be expanded upon on the fly

Sable.

• fs
  • readFile – read file and return Uint8Array
  • readTextFile – read file and return string
  • writeFile – write file using Uint8Array
  • writeTextFile – write file using string
  • removeFile - delete file
  • removeDirectory - delete directory
  • copyFile - copy file
  • copyDirectory - copy directory
  • moveFile - move/rename file
  • moveDirectory - move/rename directory
  • makeDirectory - create a new directory
  • makeFile - create a new file
  • makeTempDirectory - create a new temporary directory in /tmp
  • makeTempFile - create a new temp file in /tmp
  • watch - create iterable which yields changes in file system
• io
  • read – read from resource id into given Uint8Array
  • write – async write to resource id using Uint8Array
  • stdin – interface for working with standard input
  • stdout – interface for working with standard output
  • stderr – interface for working with standard error output
• testing
  • test - test runner
  • bench - benchmark runner

[Im-Beast]

Things that are yet to be discussed:

• Sable.fs.File
• Sable.io.{Stdin, Stdout, Stderr}
• Sable.io.{write, writeSync, read, readSync} – should they even exist?