On 11/12/12 8:04 AM, Brian Burg wrote:
In the case of rust bindings to other APIs (which is what most of the
submodules are), separate repositories and crates make sense.
For parts of servo like gfx, css, dom, and layout, I think it makes
sense to put them in separate crates but in the same repo
In the case of rust bindings to other APIs (which is what most of the
submodules are), separate repositories and crates make sense.
For parts of servo like gfx, css, dom, and layout, I think it makes sense to
put them in separate crates but in the same repository. I'm mostly averse to
splitting
On Sun, Nov 11, 2012 at 8:25 PM, Brian Burg wrote:
> As submodules stand now, it's getting quite hard to understand the project
> history, as it's scattered across 30 git logs.
>
Perhaps I am missing something here but is it necessary to have only one
rust create per git repository? Must they be
On 11/11/12 8:25 PM, Brian Burg wrote:
In what sense are any of these things (outside of utility-like data
structures) reusable? Or, is it possible to swap out one
implementation for another? Is this just a workaround for lacking
incremental compilation? Do we want to encourage modularity at the
In what sense are any of these things (outside of utility-like data structures)
reusable? Or, is it possible to swap out one implementation for another? Is
this just a workaround for lacking incremental compilation? Do we want to
encourage modularity at the task or functionality boundaries?
Alm
Just FYI, I've split out GFX and all its dependencies (image, resource,
text, most of util) into the servo-gfx crate as a submodule. This means
that if you're just modifying layout you can avoid rebuilding some ~5000
lines of code of the graphics module.
The resource crate and util should furt
6 matches
Mail list logo
