Those would serve, certainly. But won't they vary from run to run for
reasons outside our control? I'd be a little more comfortable keeping the
id's deterministic, if it's not a big deal.
On Tue, Dec 13, 2016 at 8:58 AM, Nick Fitzgerald
wrote:
> We already have IDs for GC things that are stabl
We already have IDs for GC things that are stable across moving GCs, but
I'm not 100% sure they are exposed in JSAPI.
Aha, looks like it is exposed:
http://searchfox.org/mozilla-central/rev/594937fec2e2fc45fa9308ba2fb964816631f017/js/public/RootingAPI.h#660
On Mon, Dec 12, 2016 at 9:10 PM, Jim Bl
Honestly, I've never liked the devtools server's practice of using weakmaps
for every little thing. They're expensive, and the Debugger itself is
already using weakmaps internally for the association from real debuggee
things to their Debugger shadows, and guarantees distinct shadows for each
(debu
For the Servo debugger, we need some kind of IPC layer:
The debugger server (i.e. the thing that talks the Chrome debugging
protocol) needs to live in the same process (and perhaps even the same
thread) as the constellation; it needs to work closely with the
constellation to figure out which scrip
4 matches
Mail list logo
