Hey Andrew,
I'm not sure if this is an design choice but i though i'll just leave that here.

I'm using Requires in many methods which get called on multiple threads/tasks a massive amount of times. Since all methods in Requires have a string in their parameter i end up allocating thousands if not millions of string objects.
Are there any thoughts to mitigate this for this library or am I just "abusing" this library ;)

Cheers!