Add ansi escape codes

[csos95]

No description provided.

[SeanTAllen]

I don't understand what you mean by this.

[rhagenson]

I do not understand this under the "Alternatives" section.

[rhagenson]

I left some comments mostly about use of default values, additional functionality, preventing errors, and my opinion on the direction I would prefer.

[rhagenson]

I do not understand this under the "Alternatives" section.

[jemc]

As discussed in the sync call, I'd like to request that the RFC include the method signatures for the new methods.

[SeanTAllen]

Suggested change

	- The `clear` function moves the cursor to the top left and then clears the screen.
	This may have been done to create the same result that this escape code gave on DOS.
	- The `clear` function moves the cursor to the top left and then clears the screen.
	This may have been done to create the same result that this escape code gave on DOS.

[csos95]

If that extra newline is added, the next line would be split out into a separate paragraph instead of being attached to the bullet point about the functionality of the current clear function.

[SeanTAllen]

Suggested change

	for the parameters.
	To enforce the safety of these functions using the type system, four primitives
	for the parameters.
	To enforce the safety of these functions using the type system, four primitives

[SeanTAllen]

During sync we discussed that we'd like to see more detailed information about function signnatures for new methods.

[rhagenson]

Thank you for splitting the modifications into a separate RFC! As well, thank you for adding example codes inline within the added escape codes list -- it is far easier to cross-reference the suggestions here with escape code tables now.

As this RFC stands I see no reason against these additions, although (as discussed on sync by Joe) I would like to see the API being suggested.