Issue 28 feature

[grosch]

Implements #28

[grosch]

You know you want it...

[jessesquires]

lol 😆

Thanks @grosch ! 😄

A few notes:

• 👍 for the Cocoa* additions. For the others, I'm not sure these should be included in the library. Let's merge only the Cocoa* typealiases for now.
• Really hate to block on this, but the commit history is particularly dirty here, looks like there are 3 unrelated commits? 😁

[grosch]

OK, so I hate github, and I never use it for anything but you. What I really need is for your contributing page to have explicit instructions. It needs to start with the "I had my own fork of your stuff. So first I need to update to make mine look exactly like you, then I do my code, then I do thing X to make it look the way you want, and then I submit the pull request"

[jessesquires]

OK, so I hate github

😆 I'm sorry!

What I really need is for your contributing page to have explicit instructions.

I'll work on this! 👍

---

So, the merging/rebasing on develop is technically optional. This really only needs to happen if there are conflicts. So maybe try this flow instead:

1. Make your changes
2. Submit a PR

If there are no conflicts, we can merge and you don't have to do anything else special. If there are conflicts, then GitHub will note this and we can handle it.

This shouldn't have any conflicts. Looks like all we need is 08083e5. If you undo the previous commits and update the branch, we should be good.

Also, sometimes it's just easier to make a new branch, copy-pasta 🍝 your changes and make a fresh commit, then submit the PR 😄

[jessesquires]

Thanks @grosch ! 😄

GitHub now squashes commits for PRs, so 🎉 🎉