Re: [dev-servo] Crazy idea: CSS selector JITting at parse time

2014-03-31 Thread Niko Matsakis
On Mon, Mar 31, 2014 at 08:11:32AM -0700, Patrick Walton wrote: > I also realized yesterday that one could just re-parse the style > sheet into the AST if the CSSOM or debugging tools are used. I wonder > whether that would be just as fast as disassembling. Good point. I imagine perf of parsing is

Re: [dev-servo] Crazy idea: CSS selector JITting at parse time

2014-03-31 Thread Niko Matsakis
Interesting thought. You could also use an embedding involving either coded no-ops at the start of each instruction and/or an unconditional jump over some meta-data. This would reduce coupling at the cost of somewhat more memory. Naturally you'd want to measure the effect on performance too, though

Re: [dev-servo] JS guide

2014-03-05 Thread Niko Matsakis
Note: the first PR related to overloadable deref has landed. This means that the `get()` and `get_mut()` methods can go away and be replaced with an overloaded `*` operator. For now, the derefs must be explicit. I'm still reviewing the second part of this work, which integrates with auto-deref. B

Re: [dev-servo] Removing shared boxes from the DOM

2013-12-06 Thread Niko Matsakis
On Fri, Dec 06, 2013 at 12:51:26PM -0800, Patrick Walton wrote: > Devirtualization isn't necessary if we use unboxed closures. Yes, I was thinking the same thing. Interesting. Niko ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mo

Re: [dev-servo] Removing shared boxes from the DOM

2013-12-06 Thread Niko Matsakis
On Fri, Dec 06, 2013 at 10:17:40AM -0800, Patrick Walton wrote: > Wouldn't these data structures be instead traced by the JS GC? ISTM > if you are putting roots in a data structure it is best to make the > data structure itself traced. This is not necessarily the case -- creating a new kind of GCT

Re: [dev-servo] Removing shared boxes from the DOM

2013-12-06 Thread Niko Matsakis
On Thu, Dec 05, 2013 at 09:27:03AM -0800, Patrick Walton wrote: > This is great stuff, thanks. Have you given thought to how the > rooting API would work? That's one of the last major pieces to making > the Servo DOM type- and memory-safe. Just to summarize what you and I talked about on IRC for t

Re: [dev-servo] Event loop and compositor communication

2013-11-02 Thread Niko Matsakis
At a high level, it seems reasonable, but I don't have a good grasp over what kinds of messages are going over these channels and with what frequency. That seems to be crucial with respect to judging the perf effects of moving to a serialization scheme. Niko On Fri, Nov 01, 2013 at 10:54:32PM -