sanny-io

I'd love to have this.

This is a breaking change.

These function names sound like they modify the existing object, but instead, they create a new one. And another thing, you should be using the named fields on the objects...

>I was thinking if I should make them modify the original or return a new object. I agree that such naming is inconsistent with vector/angle normalization/rotation functions naming, though there...

In my opinion, yes, but I don't want to be picky. If the core devs think they should be changed to something else, I'm sure they'll ask.

Promises are extremely useful. This should be in the `util` library, however. `util.Promise` instead of `promise.New`

@thegrb93 this is for anything that is asynchronous, of which there are many things...database queries, net messages, external API calls.

It isn't done that way because gsub errors if the value in the table is something other than a string or a number.

Sure, I'll try to do that this week.

Also having this issue on 4.2.5