I feel the change would also affect these points:
https://github.com/servo/servo/blob/master/src/components/layout/flow.rs#L277
https://github.com/servo/servo/blob/master/src/components/layout/flow.rs#L290
2014-08-27 7:17 GMT+09:00 Jack Moffitt :
> There are at least two cases of this, both curre
On Aug 26, 2014, at 8:39 PM, Patrick Walton wrote:
> On 8/26/14 4:25 PM, Cameron Zwarich wrote:
>> Cons:
>> - Still requires an abstraction layer for features that differ across
>> platforms, unless we fix a target platform.
>> - There is a semantic gap between OS I/O primitives and Rust channel
On 8/26/14 4:25 PM, Cameron Zwarich wrote:
Cons:
- Still requires an abstraction layer for features that differ across
platforms, unless we fix a target platform.
- There is a semantic gap between OS I/O primitives and Rust channels, and the
problem of having a task that processes events from b
Take the comments below with a grain of salt - coming from a games
background, I am still learning about the complexities of browsers and
thus it's likely I'm over-simplifying things :)
When we first looked at the challenge of taking a single threaded game
engine and making it multi-threaded,
On Wed, Aug 27, 2014 at 11:25 AM, Cameron Zwarich
wrote:
> 1) Script task completes execution.
>
> 2) Some external stimulus triggers layout.
>
> 3) Flow tree construction takes the DOM lock, creates the flow tree, and
> releases it.
>
> 4) Before layout actually begins, the script task begins ex
Due to the recent news from the Rust workweek regarding the pending removal
libgreen from the standard distribution (and any support in related libraries
like I/O, locking, etc. that goes with it) there has been a bunch of discussion
about Servo’s use of threads and tasks. This discussion has ta
There are at least two cases of this, both currently annotated with FIXME:
https://github.com/servo/servo/search?utf8=%E2%9C%93&q=TraitObject
Thanks for the heads up!
jack.
On Tue, Aug 26, 2014 at 4:14 PM, Nick Cameron wrote:
> For the next Rust upgrade you should be aware of a subtle breaking
For the next Rust upgrade you should be aware of a subtle breaking change -
the compiler's internal representation of trait objects has changed.
Previously trait objects were represented as a pair of pointer-to-vtable,
pointer-to-data. That order has been reveresed to pointer-to-data,
pointer-to-vt
8 matches
Mail list logo
