to match the
crates.io version numbers?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
’d be open to
accepting PRs to https://github.com/bnjbvr/botzilla
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 09/01/2020 22:33, Josh Matthews wrote:
After coming across an instance of a non-snake case variable name that
didn't trigger any compiler warnings, I discovered that we disabled that
warning for the script crate 5 years ago
On 20/12/2019 17:41, Josh Bowman-Matthews wrote:
One more IRC integration that I forgot about - we receive notifications
about daily taskcluster job failures on IRC. We'll want to verify the
plans for the taskcluster-notify service with respect to Matrix.
I asked:
Hi. What’s the future
work but seems doable.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
will remain closed until mac3
can either be removed from the pool of workers or repaired.
I’ve (hopefully) fixed this and reopened the tree:
https://github.com/servo/servo/issues/24755#issuecomment-554619776
--
Simon Sapin
___
dev-servo mailing list
dev-servo
TPAC, W3C’s yearly gathering, happens in a couple weeks:
https://www.w3.org/2019/09/TPAC/schedule.html
I plan to attend the meetings for the CSS WG, the SVG WG, and the
Houdini TF. Let me know if you have topics that I should bring to either
of those groups’ attention.
--
Simon Sapin
://github.com/rust-lang/cargo/issues/5376
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 03/04/18 23:30, Emilio Cobos Álvarez wrote:
or the bit to use the gold linker.
The best outcome IMO would be to make that the default:
https://github.com/rust-lang/rust/issues/30783
This was implemented and then reverted because of Debian Wheezy
(oldoldstable), whose LTS ends next month
about try builds (where you can maybe be
satisfied when the grid mostly green) and did not mean to suggest
bypassing homu when it’s time to actually land something.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https
it be removed?
Oops. Yes, this file should stay. Besides that, I *think* you should
only have .cargo/git and .cargo/registry. These are the download cache
for dependencies.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https
dependencies.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 23/12/17 20:54, Enrico Weigelt, metux IT consult via dev-servo wrote:
I'm using a pretty fresh rustc
I’ve responded in https://github.com/servo/servo/issues/19637. Please
pick one of the mailing list or issue tracker for each topic, and avoid
duplicating discussions.
--
Simon Sapin
in the current scope.
https://doc.rust-lang.org/book/second-edition/ch07-00-modules.html
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
for installing rustup in our README, and
again an error message when mach cannot find a `rustup` executable.
The `system-rust = true` configuration would remain available and run
plain `cargo` or `rustc` like before.
Thoughts?
--
Simon Sapin
___
dev-servo
On 01/11/17 22:25, Josh Matthews wrote:
In short, I think we should enable the new testsuite, remove the old
tests and related CI jobs, and never look back! The ability to upstream
reftests and share others' improvements will be a significant boon.
Great news! Thanks for working on this.
--
.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 18/10/2017 23:26, Simon Sapin wrote:
Anyway, some of the affected commits have a rust-toolchain or
rust-nightly-date file that contains a date. You can then run something
like `rustup override set nightly-2017-10-13` to get that version and
tell rustup to use it when under the current
out making a call and catching
some exceptions, but that seems fragile. We’re not using the ssl module
directly.
So now, `if HAS_SNI and sys.version_info >= (2, 7, 9)`, we use the
CloudFront hostname with root CAs from the certifi package. Otherwise we
use the unofficial S3 hostname.
--
. (Nighties in rustup are indexed by date of
publication, but are picked from the last merge before midnight, so on
the previous day.)
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 18/10/2017 22:37, Gregory Szorc wrote:
On Wed, Oct 18, 2017 at 10:01 PM, Simon Sapin <simon.sa...@exyr.org> wrote:
try:
from ssl import HAS_SNI
except ImportError:
HAS_SNI = False
[…]
https://static-rust-lang-org.s3.amazonaws.com/ is what we use at the
ust-lang-org.s3.amazonaws.com/ is what we use at the moment.
I’ll discuss with the Rust team to see if they’re willing to commit to
supporting some non-SNI hostname.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
ht
and configuring working Rust and Cargo
versions if we ever need to build an old Servo version?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
enough default version since Debian 8.0 Jessie
released in April 2015, and Ubuntu since Vivid Vervet 15.04 released in
April 2015.
Travis-CI still uses Ubuntu 14.04 LTS, but using 'language: python' in
.travis.yml gives an environment with a recent enough Python version.
Thoughts ?
--
Simon
URL
schemes?)
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
we want to make
breaking changes to heapsize.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
mpiled) soon after upgrading
rustc (so possibly with no relevant incremental cache entries) to
1.22.0-nightly (c6884b12d 2017-09-30).
5x slower than what?
Slower than the same with incremental disabled. Seven and a half minutes
(incremental = true) vs one and a half (incremental = f
from making a read
code change. Maybe the red/green system will change that?
A real change that could occur during debugging and that’s easy to
reproduce at any base commit is adding println!("{:#?}", some_variable)
at a random place in the code.
--
Simon Sapin
__
lk by Niko explains the new query-based approach for compiler
internals:
https://skillsmatter.com/skillscasts/10868-inside-the-rust-compiler
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
t mentions
the number of the PR being reverted, which is good.
It should also comment on *that* PR to let the people involved that
they’ll have something to fix and they’ll need to try to land this
again. We don’t want improvements being forgotten after being backed out.
--
S
/the-story-of-firefox-os-cb5bf796e8fb
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
`mach cargo check` is worth listing in Servo's README.md, IMO!
https://github.com/servo/servo/pull/16854 adds `mach check` and `mach
check-geckolib`, and mentions the former in README.
--
Simon Sapin
___
dev-servo mailing list
dev-servo
On 31/03/17 19:43, Simon Sapin wrote:
# cargo check
Remember how I said a crate needs its dependencies to be compiled before
it can start compiling? It actually only needs metadata (the results of
the analysis phase), not the generated code.
Cargo added a `cargo check` command that skips code
rvo/servo/pull/15565
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
comments anyway :)
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
g to issue numbers without these
keywords.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
for
review, please do so in a subsequent comment on a pull request, not in a
commit message or initial pull request message.
Thanks!
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
t only has a readme file that says the source is
now at https://github.com/servo/servo/tree/master/components/selectors.
The master branch and issue / PR tracker are still there if we need them.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.m
/servo/rust-selectors and
made it the default. It only has a readme file that says the source is
now at https://github.com/servo/servo/tree/master/components/selectors.
The master branch and issue / PR tracker is still there if we need it.
--
Simon Sapin
ntributing
to Gecko also requires jumping through a number of (different) hoops.)
I’m inclined to concede, but I’d like to hear from other people before
hitting the button.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla
trigger a try
push,
I think we can and should improve tooling here. One command to add a
replacement/override, one command to start a try build.
[...] and then publish to crates.io, [...]
I think we should make Travis-CI publish to crates.io when we merge a
version number change to m
coherence require them to be, while
keeping the bindgen-using build script in a dedicated crate.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
There's just
`Vec`, which is used in Stylesheet[1], MediaRule[2],
and @supports rules (not supported in servo yet).
There isn’t yet (in master) but as you did in #14190 the idea is to
introduce Arc’s (and RwLock’s) as needed. (That is, unless we get rid of
t
.
There is a proposed Font Metrics API that does this:
https://drafts.css-houdini.org/font-metrics-api/
It is still in early exploratory stages. Please send feedback on this
API as indicated near the top of the draft.
--
Simon Sapin
___
dev-servo mailing list
dev
s are conditionally-complied
re-exports of gecko_string_cache::Atom, which is unchanged.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
.
--
Simon Sapin
--
You received this message because you are subscribed to the Google
Groups "stylo-team" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to stylo-team+unsubscr...@mozilla.com.
To post to this group, send email to stylo-t...@mozilla.co
not XHTML)" one.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 24/08/16 18:37, Simon Sapin wrote:
Some files (some of them relatively large, like
reference/support/big-buck-bunny-240p.webm) are also duplicated across
multiple specs.
Looks like even within on spec, /support and /reference/support have
some duplication. We should merge those too
the latter to skip painting such elements.
Maybe it could add a way to query that information? Or maybe display
lists already carry that information, without going to webrender?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https
/crates/wayland-client
Beyond that, crates.io was unavailable for a while yesterday. Maybe that
impacted you?
What’s the full output you get when building Servo?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https
it may unexpectedly break in the future.
Why isn’t this supposed to work? Based on conversations with Alex, Cargo
by design builds a crate with the union of all requested features. There
is no need for all dependents to specify the same set of features and
this isn’t an accide
tureful graphics than fbdev. And i did not have the
exact nightly used by the build script, too.
Servo does do a lot of stuff of the GPU, but I don’t know the exact
requirements.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.m
Hi all,
I have a pull request for rust-url with large breaking changes:
https://github.com/servo/rust-url/pull/176
I’d appreciate feedback (preferably in github comments) on the API design.
Thanks!
--
Simon Sapin
___
dev-servo mailing list
dev
://wiki.mozilla.org/IRC
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
the other way around?
How long would it typically take between approving a GitHub PR and
having it land in GitHub master? (This matters when a conflicting PR
needs to be rebased.) Would it be blocked on mozilla-inbound being
merged into mozilla-central?
--
S
nverge with some of these?
[1] https://github.com/servo/rust-smallvec
[2]
https://github.com/SimonSapin/rust-std-candidates/blob/master/string-wrapper/lib.rs
[3] https://github.com/SimonSapin/rust-utf8
--
Simon Sapin
___
dev-servo mailing list
dev
at do you think of making it advisory rather than a hard requirement?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 23/10/15 05:43, Pranesha Shashwath Kumar Kattepura Jayabheema Rao wrote:
Python virtualenv failed to execute properly.
Try removing the python/_virtualenv directory, it should be re-created
automatically next time you run ./mach build
--
Simon Sapin
.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
part of the WPT suite.
./mach build -r
./mach test-wpt -r
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
.gz>)
in the meantime.
If you also have a clone of the Servo repository, you can use its Rust
snapshot (which is downloaded automatically) by using e.g.
`../servo/mach cargo` instead of `cargo`.
--
Simon Sapin
___
dev-servo mailing list
dev
On 01/09/15 10:15, Anthony Ramine wrote:
I can be the second person on h5e, if you want.
That’s great, thanks!
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Areas of code", to start, could be each crate in the
servo/servo repository and each other repository in the servo org on github.
Of course we may not be able to reach this ideal state yet, but we
should still go towards it.
--
Simon Sapin
___
dev-ser
of a single alphabetical-order group.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
at
all), so old Servo commits should still build.
We should still update to the new name, though, and use the crates.io
copy to force ourselves to keep it up-to-date. I’ve filed
https://github.com/servo/servo/issues/6406 about this.
--
Simon Sapin
for packages whose source is under https://github.com/servo .
Who should that be? Everyone on
https://github.com/orgs/servo/teams/owners ? Everyone on
https://github.com/orgs/servo/people ? Some other set of people? Or
something different for each package, based on people’s area of interest?
--
Simon
that depends on bswap? In the Rust version that Servo
uses right now, that functionality is part of the standard library’s
std::old_io::Reader and std::old_io::Writer and the bswap library did
not exist yet.
--
Simon Sapin
___
dev-servo mailing list
dev-servo
As far as I understand, this proposes adding control on what phases of
rendering of what parts of the document can be deferred or (de)prioritized.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo
returns early on
`Err`) to make the code easier to read and maintain. (For what it’s
worth, the diff stat is +1,949/-2,319 lines.)
Finally, string components of tokens now use the `CowString` type to
borrow from the input when possible and avoid many allocations and lots
of copying.
--
Simon
, likely some time in January) of this
page:
https://wiki.mozilla.org/Community:SummerOfCode14:Brainstorming
We can still start gathering ideas, of course.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org
CSS transforms.
(Still, this is more of an exception than a common case.)
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
the way through, with a couple of different available inline sizes.
[1] http://dev.w3.org/csswg/css-sizing/#block-intrinsic
This means using results (for a subtree) of our third traversal in the
first traversal. Can we do that without compromising parallel layout?
--
Simon Sapin
is entirely based on the assumption that we can give any meaning we
want to input sequences that used to fail to parse.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 06/10/14 07:57, Henri Sivonen wrote:
On Sun, Oct 5, 2014 at 7:26 PM, Simon Sapin simon.sa...@exyr.org wrote:
JavaScript strings, however, can. (They are effectively potentially
ill-formed UTF-16.) It’s possible (?) that the Web depends on these
surrogates being preserved.
It's clear
something out for .charAt() and friends), SpiderMonkey could support
WTF-8 internally for JS strings and Servo’s bindings could remove the
conversion.
What do you think?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https
On 15/09/14 05:13, Matt Brubeck wrote:
Today's Cargo nightly contains some recent fixes [...]
Which version is that? I just updated to 3f6af3d 2014-09-13, which may
or may not be today’s because of
https://github.com/rust-lang/rust/issues/16649
--
Simon Sapin
/rust/issues/16328
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
to the reader. Input welcome on potential improvements.”
I suppose event dispatching is relevant too.
Anyone wants to take a look? Feedback on the spec should filed in its
bug tracker (see the “file a bug” link at the top), or annevk can be
found on IRC #whatwg @ Freenode.
--
Simon Sapin
-url origin g...@github.com:servo/rust-url.git
Cheers,
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Hi all,
Can someone help this person with Servo on Android? Please keep them in
CC as they’re probably not subscribed to the list.
Thanks,
--
Simon Sapin
On 10/07/14 14:39, Cristian Silaghi wrote:
Can you share with me one recent build of Servo for Android? I want to
test it on my phone
principle to decide how many structs to have, and
which properties go where? Why not have every longhand property in its
own struct, sharable separately? Is there something you’d like to
change in Gecko’s distribution, but don’t because making the change
would be too painful?
--
Simon Sapin
to have a different ideas of what
flow-relative means. Is there a reason for this?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 27/05/2014 18:14, Patrick Walton wrote:
On 5/26/14 3:11 PM, Simon Sapin wrote:
I’m fine with that, but I’m more interested in the signature than the
naming. That is, which of these (or others) to have, for each private
field?
fn(self) - T
fn(mut self, T)
fn('a mut self) - 'a mut T
Hmm. My
to do accessors in Rust?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 26/05/2014 22:52, Patrick Walton wrote:
On 5/26/14 2:44 PM, Simon Sapin wrote:
Unlike C++, Rust does not have method overloading so the accessors are
much more verbose.
`nscoord ISize(WritingMode aWritingMode) const` overloaded with
`nscoord ISize(WritingMode aWritingMode)` becomes
the spec that way, a few years ago:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=11298#c2
Henri, any comment?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
On 29/03/2014 23:15, Boris Zbarsky wrote:
On 3/29/14 6:56 PM, Simon Sapin wrote:
Or I guess we could use what I’ll call evil UTF-8, which is UTF-8
without the artificial restriction of not encoding surrogates.
http://en.wikipedia.org/wiki/CESU-8
CESU-8 is evil too, but it’s not what I had
On 29/03/2014 22:56, Simon Sapin wrote:
On 10/03/2014 23:54, Keegan McAllister wrote:
Speaking of which, [5]
Any character that is a not a Unicode character, i.e. any isolated
surrogate, is a parse error. (These can only find their way into
the input stream via script APIs
Unfortunately I’d be less surprised if someone relies on having the two
halves of a surrogate pair in separate document.write() call, as this
seems more interoperable:
data:text/html,scriptdocument.write(\uD83D);document.write(\uDCA9)/script
--
Simon Sapin
be confident that the
cast will succeed or task failure will occur.
Would it make sense to have downcasting return an option? That way you
can either match to have different behavior in either case, or use
.unwrap() when you expect success.
--
Simon Sapin
of today, which helps us answer the
big questions that Servo set out to answer.
Yes, Web compat is important. But Acid3 in particular is a poor proxy
for Web compat, IMO.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https
review is probably to make a pull request. We have
tools that make tracking the review much easier then.
(Also, if you use IRC at all, you should join #servo on irc.mozilla.org :))
Cheers,
--
Simon Sapin
___
dev-servo mailing list
dev-servo
and the content tree to script.
Not the tree itself. DOM tree is a misuse IMO, although the data model
for the content tree is necessarily closely tied to the DOM.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https
types.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
between CSS px and device
pixels, exactly like zooming. Shouldn’t it just be different default zoom?
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Le 29/10/2013 17:22, Patrick Walton a écrit :
On 10/29/13 8:52 AM, Simon Sapin wrote:
Le 29/10/2013 15:06, Josh Matthews a écrit :
https://github.com/mozilla/servo/wiki/Meeting-2013-10-28
Retina display
P: In the short term, we should change the Au that CSS reports.
I disagree. Au as I
W3C and Gecko.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
just use Servo for now, and revisit this when we actually
worry about being compatible with the long tail of websites.
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
to
rewrite the layout code to use logical keywords (eg. measure/extent
instead of width/height) while we don’t have much layout code.
http://dev.w3.org/csswg/css-writing-modes/
http://dev.w3.org/csswg/css-writing-modes/#abstract-box
--
Simon Sapin
1 - 100 of 106 matches
Mail list logo
