Rework rustc_serialize

[matthewjasper]

Proposal

rust-lang/rust#73851 reworks specialization in the following noticeable ways:

• The type parameter in the Encodable and Decodable traits is moved from the method to the trait.
• These traits are now derived using macros in rustc_macros rather than the built-in RustcEncodable and RustcDecodable derives.
• Specialized implementations of Encodable and Decodable now directly use specialization.
• A lot of transmutes are removed

Further documentation of serialization in rustc after the PR has landed can be found at rust-lang/rustc-dev-guide#785.

Mentors or Reviewers

PR has already been reviewed by @oli-obk

Process

The main points of the Major Change Process is as follows:

• File an issue describing the proposal.
• A compiler team member or contributor who is knowledgeable in the area can second by writing @rustbot second.
  • Finding a "second" suffices for internal changes. If however you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
  • Compiler team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.
• Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

Comments

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

[rustbot]

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

[oli-obk]

@rustbot second

[extf33]

@matthewjasper

Hello, I came across this issue while looking for a way to serialize/deserialize the MIR Body.
I have two questions.

1. Where in the rustc code is the decode() method, which is associated with the MIR Body (as mentioned below), used?

   • https://github.com/rust-lang/rust/blob/04374cd74264b9d3b7d2d3df08ae38df8af4d020/compiler/rustc_middle/src/ty/codec.rs#L420
   • https://github.com/rust-lang/rust/blob/04374cd74264b9d3b7d2d3df08ae38df8af4d020/compiler/rustc_middle/src/ty/codec.rs#L266-L275
   • https://github.com/rust-lang/rust/blob/04374cd74264b9d3b7d2d3df08ae38df8af4d020/compiler/rustc_middle/src/query/on_disk_cache.rs#L787-L794

2. Is it possible to serialize the MIR Body to a file (during a MIR pass) and then load it back by deserializing it?
   If so, how should the code be written?
   I thought of a logic like the one below.

   use crate::MirPass;
   use rustc_middle::mir::*;
   use rustc_middle::ty::TyCtxt;
   use rustc_serialize::opaque::{FileEncoder, MemDecoder};
   use rustc_serialize::{Decodable, Encodable};
   use std::fs;
   
   pub struct MirSerDe;
   
   impl<'tcx> MirPass<'tcx> for MirSerDe {
       fn run_pass(&self, _tcx: TyCtxt<'tcx>, body: &mut Body<'tcx>) {
           let tmpfile = tempfile::NamedTempFile::new().unwrap();
           let tmpfile = tmpfile.path();
   
           // Serialize
           let mut encoder = FileEncoder::new(&tmpfile).unwrap();
           Encodable::encode(body, &mut encoder);
           encoder.finish().unwrap();
   
           // Deserialize
           let data = fs::read(&tmpfile).unwrap();
           let mut decoder = MemDecoder::new(&data[..], 0);
           let decoded = Decodable::decode(&mut decoder);
   
           assert_eq!(body, decoded);
       }
   }