I think that approach makes sense if `predictableFuncName` is replaceable. In this context, it really isn't, which is why I figure you can just shortcut to the specific, purpose-tied name. The specific one answers “what do I get” both generally (it's predictable) and specifically (it's from the stack). This can be useful because there are cases where the predictable generator actually is too predictable—you can get duplicates at times, leading to weird behavior—and knowing that it comes from the stack trace *as a user* might help tell you what weirdness is happening without having to get into the nitty gritty of what the framework is doing.

Basically my attitude for the framework is the less work for a *user* doing debugging, the better. I can see this helping that goal.

I don't consider it a huge deal, and other than that this PR looks good.