Anything with _ infront of it should probably not be framework-user-facing. Two reasons: 1. we want to encourage _ to mean private API, therefore 2. we want framework-users to feel dirty using it (that's why __container__ feels so messy to use). I'm sure you already know this. Can we somehow **not** use _rawFunction ? (Read the comments on this PR and conclusions weren't apparent).