I think we should approach this differently to cleanly separate concerns:
Leaving PerThreadAssertData as it is and having every scope have a
shared_ptr to
the data is describing the idea behind this CL in a much cleaner way. IIRC
we
don't have a shared_ptr in our utilities, but creating a simple one
shouldn't be
too hard and will probably come in handy later.
https://codereview.chromium.org/16093024/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
