rust/compiler/rustc_codegen_ssa/src/debuginfo, branch 1.74.0

Remove GeneratorWitness and rename GeneratorWitnessMIR.

2023-09-23T13:47:30+00:00

the Const::eval_bits methods don't need to be given the Ty

2023-09-20T05:27:21+00:00

Auto merge of #115817 - fee1-dead-contrib:fix-codegen, r=oli-obk

2023-09-14T13:42:30+00:00

treat host effect params as erased in codegen This fixes the changes brought to codegen tests when effect params are added to libcore, by not attempting to monomorphize functions that get the host param by being `const fn`. r? `@oli-obk`

treat host effect params as erased generics in codegen

2023-09-14T07:34:35+00:00

This fixes the changes brought to codegen tests when effect params are added to libcore, by not attempting to monomorphize functions that get the host param by being `const fn`.

make the eval() functions on our const types return the resulting value

2023-09-13T05:29:34+00:00

inline format!() args up to and including rustc_codegen_llvm

2023-07-30T12:22:50+00:00

refactor(rustc_middle): Substs -> GenericArg

2023-07-14T12:27:35+00:00

Use translatable diagnostics in `rustc_const_eval`

2023-06-01T14:45:18+00:00

Restrict `From` for `{D,Subd}iagnosticMessage`.

2023-05-02T22:44:39+00:00
Currently a `{D,Subd}iagnosticMessage` can be created from any type that impls `Into`. That includes `&str`, `String`, and `Cow<'static, str>`, which are reasonable. It also includes `&String`, which is pretty weird, and results in many places making unnecessary allocations for patterns like this: ``` self.fatal(&format!(...)) ``` This creates a string with `format!`, takes a reference, passes the reference to `fatal`, which does an `into()`, which clones the reference, doing a second allocation. Two allocations for a single string, bleh. This commit changes the `From` impls so that you can only create a `{D,Subd}iagnosticMessage` from `&str`, `String`, or `Cow<'static, str>`. This requires changing all the places that currently create one from a `&String`. Most of these are of the `&format!(...)` form described above; each one removes an unnecessary static `&`, plus an allocation when executed. There are also a few places where the existing use of `&String` was more reasonable; these now just use `clone()` at the call site. As well as making the code nicer and more efficient, this is a step towards possibly using `Cow<'static, str>` in `{D,Subd}iagnosticMessage::{Str,Eager}`. That would require changing the `From<&'a str>` impls to `From<&'static str>`, which is doable, but I'm not yet sure if it's worthwhile.

Store hashes in special types so they aren't accidentally encoded as numbers

2023-04-18T14:52:47+00:00