<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/src/libserialize/json.rs, branch 1.25.0</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=1.25.0</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=1.25.0'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2017-12-09T22:18:33+00:00</updated>
<entry>
<title>Use Try syntax for Option in place of macros or match</title>
<updated>2017-12-09T22:18:33+00:00</updated>
<author>
<name>Matt Brubeck</name>
<email>mbrubeck@limpet.net</email>
</author>
<published>2017-12-09T01:32:04+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=3024c1434a667425d30e4b0785857381323712aa'/>
<id>urn:sha1:3024c1434a667425d30e4b0785857381323712aa</id>
<content type='text'>
</content>
</entry>
<entry>
<title>use field init shorthand EVERYWHERE</title>
<updated>2017-08-15T22:29:17+00:00</updated>
<author>
<name>Zack M. Davis</name>
<email>code@zackmdavis.net</email>
</author>
<published>2017-08-07T05:54:09+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=1b6c9605e41b7c7dc23e0e6f633f05912d0463dd'/>
<id>urn:sha1:1b6c9605e41b7c7dc23e0e6f633f05912d0463dd</id>
<content type='text'>
Like #43008 (f668999), but _much more aggressive_.
</content>
</entry>
<entry>
<title>Removed as many "```ignore" as possible.</title>
<updated>2017-06-23T07:31:53+00:00</updated>
<author>
<name>kennytm</name>
<email>kennytm@gmail.com</email>
</author>
<published>2017-06-20T07:15:16+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=4711982314ba33cab83704c26484b501c8652774'/>
<id>urn:sha1:4711982314ba33cab83704c26484b501c8652774</id>
<content type='text'>
Replaced by adding extra imports, adding hidden code (`# ...`), modifying
examples to be runnable (sorry Homura), specifying non-Rust code, and
converting to should_panic, no_run, or compile_fail.

Remaining "```ignore"s received an explanation why they are being ignored.
</content>
</entry>
<entry>
<title>Bump version, upgrade bootstrap</title>
<updated>2017-02-03T21:25:46+00:00</updated>
<author>
<name>Alex Crichton</name>
<email>alex@alexcrichton.com</email>
</author>
<published>2017-02-01T23:57:50+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=626e754473da96a670c917b9cbefd1c1ea888a9c'/>
<id>urn:sha1:626e754473da96a670c917b9cbefd1c1ea888a9c</id>
<content type='text'>
This commit updates the version number to 1.17.0 as we're not on that version of
the nightly compiler, and at the same time this updates src/stage0.txt to
bootstrap from freshly minted beta compiler and beta Cargo.
</content>
</entry>
<entry>
<title>Implement emit_iu128 for json serialiser</title>
<updated>2016-12-30T14:17:26+00:00</updated>
<author>
<name>Simonas Kazlauskas</name>
<email>git@kazlauskas.me</email>
</author>
<published>2016-08-27T21:59:14+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=4ff620e0edd4928468e59a09e83092742082838b'/>
<id>urn:sha1:4ff620e0edd4928468e59a09e83092742082838b</id>
<content type='text'>
Causes ICEs otherwise while trying to dump AST
</content>
</entry>
<entry>
<title>Such large. Very 128. Much bits.</title>
<updated>2016-12-30T14:15:44+00:00</updated>
<author>
<name>Simonas Kazlauskas</name>
<email>git@kazlauskas.me</email>
</author>
<published>2016-08-23T00:56:52+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=b0e55a83a82bae26851f442859acace2b94f5028'/>
<id>urn:sha1:b0e55a83a82bae26851f442859acace2b94f5028</id>
<content type='text'>
This commit introduces 128-bit integers. Stage 2 builds and produces a working compiler which
understands and supports 128-bit integers throughout.

The general strategy used is to have rustc_i128 module which provides aliases for iu128, equal to
iu64 in stage9 and iu128 later. Since nowhere in rustc we rely on large numbers being supported,
this strategy is good enough to get past the first bootstrap stages to end up with a fully working
128-bit capable compiler.

In order for this strategy to work, number of locations had to be changed to use associated
max_value/min_value instead of MAX/MIN constants as well as the min_value (or was it max_value?)
had to be changed to use xor instead of shift so both 64-bit and 128-bit based consteval works
(former not necessarily producing the right results in stage1).

This commit includes manual merge conflict resolution changes from a rebase by @est31.
</content>
</entry>
<entry>
<title>Changed most vec! invocations to use square braces</title>
<updated>2016-10-31T22:51:40+00:00</updated>
<author>
<name>iirelu</name>
<email>anna@bawk.space</email>
</author>
<published>2016-10-29T21:54:04+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=e593c3b89343a98bdcc76ce9f5869ff18882dfff'/>
<id>urn:sha1:e593c3b89343a98bdcc76ce9f5869ff18882dfff</id>
<content type='text'>
Most of the Rust community agrees that the vec! macro is clearer when
called using square brackets [] instead of regular brackets (). Most of
these ocurrences are from before macros allowed using different types of
brackets.

There is one left unchanged in a pretty-print test, as the pretty
printer still wants it to have regular brackets.
</content>
</entry>
<entry>
<title>Avoid allocations in `Decoder::read_str`.</title>
<updated>2016-10-09T23:36:35+00:00</updated>
<author>
<name>Nicholas Nethercote</name>
<email>nnethercote@mozilla.com</email>
</author>
<published>2016-10-09T22:07:18+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=b043e11de2eb2c60f7bfec5e15960f537b229e20'/>
<id>urn:sha1:b043e11de2eb2c60f7bfec5e15960f537b229e20</id>
<content type='text'>
`opaque::Decoder::read_str` is very hot within `rustc` due to its use in
the reading of crate metadata, and it currently returns a `String`. This
commit changes it to instead return a `Cow&lt;str&gt;`, which avoids a heap
allocation.

This change reduces the number of calls to `malloc` by almost 10% in
some benchmarks.

This is a [breaking-change] to libserialize.
</content>
</entry>
<entry>
<title>[breaking-change] std: change `encode_utf{8,16}()` to take a buffer and return a slice</title>
<updated>2016-09-28T07:03:30+00:00</updated>
<author>
<name>tormol</name>
<email>t.b.moltu@lyse.net</email>
</author>
<published>2016-09-08T11:54:39+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=13a2dd96fe824cc5d61e94ed380db0114efdd014'/>
<id>urn:sha1:13a2dd96fe824cc5d61e94ed380db0114efdd014</id>
<content type='text'>
They panic if the buffer is too small.
</content>
</entry>
<entry>
<title>Use question_mark feature in libserialize.</title>
<updated>2016-09-11T23:02:43+00:00</updated>
<author>
<name>Ahmed Charles</name>
<email>acharles@outlook.com</email>
</author>
<published>2016-08-27T14:16:17+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=d73e374ddbf66489c0565566d26e659e6ff80c2c'/>
<id>urn:sha1:d73e374ddbf66489c0565566d26e659e6ff80c2c</id>
<content type='text'>
</content>
</entry>
</feed>
