bors f893495e3d Auto merge of #98957 - RalfJung:zst-are-different, r=lcnr,oli-obk ... don't allow ZST in ScalarInt There are several indications that we should not ZST as a ScalarInt: - We had two ways to have ZST valtrees, either an empty `Branch` or a `Leaf` with a ZST in it. `ValTree::zst()` used the former, but the latter could possibly arise as well. - Likewise, the interpreter had `Immediate::Uninit` and `Immediate::Scalar(Scalar::ZST)`. - LLVM codegen already had to special-case ZST ScalarInt. So I propose we stop using ScalarInt to represent ZST (which are clearly not integers). Instead, we can add new ZST variants to those types that did not have other variants which could be used for this purpose. Based on https://github.com/rust-lang/rust/pull/98831. Only the commits starting from "don't allow ZST in ScalarInt" are new. r? `@oli-obk`		2022-07-09 17:16:00 +00:00
..
src	Auto merge of #98957 - RalfJung:zst-are-different, r=lcnr,oli-obk	2022-07-09 17:16:00 +00:00
Cargo.toml	Initial fixes on top of type interner commit	2022-05-28 11:38:22 -07:00