doc: mark assert.CallTracker experimental

[BridgeAR]

Some details might still change and it would be good to get feedback
from users before we mark this as stable.

It might for example be good to rework the stack property.

Signed-off-by: Ruben Bridgewater [email protected]

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

[jasnell]

Won't block this but I don't see it as strictly necessary. If additional useful changes are to be made, then let's identify those and get them in. It's still brand new API that very few are no one is using yet because it has not yet gone out in a release.

[juanarbol]

LGTM

[Trott]

Doing this is a very good idea. My big concern with pretty much all new APIS is that we may find that we've made an API design mistake. Once people start using it, it may become apparent that there is a more ergonomic way to do things. And I'm also often concerned that we may not name APIs the best we can. Let's leave ourselves a little wiggle room for a few releases. If it goes out as Experimental in, say, 14.2.0, we can always remove Experimental in a later 14.x release.

[targos]

Landed in c81e5f6

[codebytere]

This is blocked until assert.CallTracker itself is backported to v12.x i believe?