Levi Morrison

I understand this may just be an example, but I highly doubt that you'd want to share any employee classes at all. This makes it more difficult to understand why...

I think my opinion is that things should not be shared twice. I think we've already had a ticket on this issue, haven't we? I think sharing something twice should...

Auryn intentionally does not make children from definitions of their parents. As mentioned in chat the other day this tends to come up often, so we should make a FAQ...

The FAQ should also provide alternatives. Sometimes it is appropriate to `alias`; sometimes not. What other choices are there?

I actually recommend that you *don't* use this library. To quote from the README: > This project is unstable and subject to significant changes from release to release. Stability is...

If it only uses `Hashable` then primitives types don't work. Also, inevitably people want to store objects in multiple ways and the `Hashable` interface has no way to indicate that...

This detail was intentional at the time it was made. Collection has changed quite a bit over time so I'll re-examine it to see if it still makes sense to...

I'm leaning more towards omitting the `get`, but you guys do bring up some good points. I will continue to think about this.

`Queue` and `Stack` are already distinct and you could implement both.

I am still not sure what to do here. Leaving open.