Guillaume Gomez 208f6ed95c Rollup merge of #115972 - RalfJung:const-consistency, r=oli-obk ... rename mir::Constant -> mir::ConstOperand, mir::ConstKind -> mir::Const Also, be more consistent with the `to/eval_bits` methods... we had some that take a type and some that take a size, and then sometimes the one that takes a type is called `bits_for_ty`. Turns out that `ty::Const`/`mir::ConstKind` carry their type with them, so we don't need to even pass the type to those `eval_bits` functions at all. However this is not properly consistent yet: in `ty` we have most of the methods on `ty::Const`, but in `mir` we have them on `mir::ConstKind`. And indeed those two types are the ones that correspond to each other. So `mir::ConstantKind` should actually be renamed to `mir::Const`. But what to do with `mir::Constant`? It carries around a span, that's really more like a constant operand that appears as a MIR operand... it's more suited for `syntax.rs` than `consts.rs`, but the bigger question is, which name should it get if we want to align the `mir` and `ty` types? `ConstOperand`? `ConstOp`? `Literal`? It's not a literal but it has a field called `literal` so it would at least be consistently wrong-ish... ``@oli-obk`` any ideas?		2023-09-21 13:25:39 +02:00
..
collector.rs	Rollup merge of #115972 - RalfJung:const-consistency, r=oli-obk	2023-09-21 13:25:39 +02:00
errors.rs	Emit error instead of ICE when optimized MIR is missing	2023-08-30 20:43:31 +02:00
lib.rs	get rid of a bit more calls to poly_select	2023-07-06 16:50:12 +00:00
partitioning.rs	treat host effect params as erased generics in codegen	2023-09-14 07:34:35 +00:00
polymorphize.rs	rename mir::Constant -> mir::ConstOperand, mir::ConstKind -> mir::Const	2023-09-21 08:12:30 +02:00
util.rs	refactor(rustc_middle): Substs -> GenericArg	2023-07-14 13:27:35 +01:00