rust/compiler/rustc_serialize, branch stablehttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=stable2025-07-05T08:55:42+00:00use `div_ceil` instead of manual logic2025-07-05T08:55:42+00:00Folkert de Vriesfolkert@folkertdev.nl2025-07-05T06:36:27+00:00urn:sha1:ed3711ea29398b09483e4e2a3930567e9ba81d93setup CI and tidy to use typos for spellchecking and fix few typos2025-07-03T07:51:06+00:00klensyklensy@users.noreply.github.com2024-12-07T10:51:08+00:00urn:sha1:c76d032f0144b650a438ee1efba89c475e0b115bUpdate `cfg(bootstrap)`2025-07-01T17:55:49+00:00Josh Stonejistone@redhat.com2025-06-24T17:05:56+00:00urn:sha1:e851e3e16e161e624b4108b83889b3fdbd5d44ddIntroduce `ByteSymbol`.2025-06-30T10:42:27+00:00Nicholas Nethercoten.nethercote@gmail.com2025-06-01T22:59:29+00:00urn:sha1:478f8287c0e2c35cda511fd3ac01b7ac78ee7cfe
It's like `Symbol` but for byte strings. The interner is now used for
both `Symbol` and `ByteSymbol`. E.g. if you intern `"dog"` and `b"dog"`
you'll get a `Symbol` and a `ByteSymbol` with the same index and the
characters will only be stored once.
The motivation for this is to eliminate the `Arc`s in `ast::LitKind`, to
make `ast::LitKind` impl `Copy`, and to avoid the need to arena-allocate
`ast::LitKind` in HIR. The latter change reduces peak memory by a
non-trivial amount on literal-heavy benchmarks such as `deep-vector` and
`tuple-stress`.
`Encoder`, `Decoder`, `SpanEncoder`, and `SpanDecoder` all get some
changes so that they can handle normal strings and byte strings.
This change does slow down compilation of programs that use
`include_bytes!` on large files, because the contents of those files are
now interned (hashed). This makes `include_bytes!` more similar to
`include_str!`, though `include_bytes!` contents still aren't escaped,
and hashing is still much cheaper than escaping.
Add a few inline directives in rustc_serialize.2025-06-21T23:54:16+00:00Camille GILLOTgillot.camille@gmail.com2025-06-21T23:54:16+00:00urn:sha1:8e9552a6b5f05b181e9b550880d252d5282f96felibrary/compiler: add `PointeeSized` bounds2025-06-16T23:04:33+00:00David Wooddavid.wood2@arm.com2025-02-10T14:18:20+00:00urn:sha1:884d0e031a046af894b43180032c1803bb6d0834
As core uses an extern type (`ptr::VTable`), the default `?Sized` to
`MetaSized` migration isn't sufficient, and some code that previously
accepted `VTable` needs relaxed to continue to accept extern types.
Similarly, the compiler uses many extern types in `rustc_codegen_llvm`
and in the `rustc_middle::ty::List` implementation (`OpaqueListContents`)
some bounds must be relaxed to continue to accept these types.
Unfortunately, due to the current inability to relax `Deref::Target`,
some of the bounds in the standard library are forced to be stricter than
they ideally would be.
Zero the buffer passed from `write_with`2025-04-25T05:14:27+00:00John Kåre Alsakerjohn.kare.alsaker@gmail.com2025-04-25T05:14:27+00:00urn:sha1:c8e7c6261ea5bc581a3e10323677e720bf1dc42bAdd index to the dep graph format and encode via `MemEncoder`2025-04-22T14:57:28+00:00John Kåre Alsakerjohn.kare.alsaker@gmail.com2025-03-26T06:12:00+00:00urn:sha1:c6735f92c1b7e24a434d3882d5e2dd716cbbb0d3Bump `FileEncoder` buffer size to 64 kB2025-04-10T16:52:03+00:00John Kåre Alsakerjohn.kare.alsaker@gmail.com2025-04-10T15:40:48+00:00urn:sha1:74ca12951ce22dfea4f11131f8f244038d4b5f18Convert `rustc_serialize` integration tests to unit tests.2025-03-19T21:59:50+00:00Nicholas Nethercoten.nethercote@gmail.com2025-03-03T08:40:00+00:00urn:sha1:e2320b32c5268913349549fc59972443975ceec4
Because (a) the vast majority of compiler tests are unit tests, and (b)
this works better with `unused_crate_dependencies`.