about summary refs log tree commit diff
path: root/compiler/rustc_hir
diff options
context:
space:
mode:
authorStuart Cook <Zalathar@users.noreply.github.com>2024-12-31 14:12:48 +1100
committerGitHub <noreply@github.com>2024-12-31 14:12:48 +1100
commit7da22aa6c31a74d491f15dd9d6421fb5334510e7 (patch)
tree8757870df1e174b0163aa1f6b95ee5ebb8ce5c44 /compiler/rustc_hir
parentf3748c4fe0a9d19532eef6ae6ea06ea2c25bf6a1 (diff)
parentc0d3634af87d50569e98ac19e36fb6ba44188a4b (diff)
downloadrust-7da22aa6c31a74d491f15dd9d6421fb5334510e7.tar.gz
rust-7da22aa6c31a74d491f15dd9d6421fb5334510e7.zip
Rollup merge of #134941 - workingjubilee:rustc-abi-normal, r=Noratrieb
compiler: Add a statement-of-intent to `rustc_abi`

This just documents the most basic idea of what the crate is even for in my view, rather than leaving that strewn about GitHub issues, PR reviews, and Zulip streams. In particular, I hope to make it clearer what code should go in `rustc_abi` and what should not, which is of immediate relevance to contributors.

I considered going even further and explaining ideas like "ABI compatibility", prologues, and so on. However, because of the cross-cutting nature of ABI, I think such explanations should probably live in the place for cross-cutting documents: the rustc dev guide. This is only meant to be a quick "by the way".
Diffstat (limited to 'compiler/rustc_hir')
0 files changed, 0 insertions, 0 deletions