Does wiredtiger.truncate satisfy the snapshot-isolation sematics?

In oplog cleaning, mongo use session->truncate to cleanup oldest oplogs.
Which may still be held by snapshot-manager's uncommitted_snapshots.
If session->truncate does not satisfy snapshot-isolation, snapshot-manager's uncommitted_snapshots are not dropped but the data are deleted.
If session->truncate does satisfy snapshot-isolation, link SERVER-29150 should be a problem?