Matthew Maurer 6aa89f684e Track reason for creating a ReifyShim ... KCFI needs to be able to tell which kind of `ReifyShim` it is examining in order to decide whether to use a concrete type (`FnPtr` case) or an abstract case (`Vtable` case). You can *almost* tell this from context, but there is one case where you can't - if a trait has a method which is *not* `#[track_caller]`, with an impl that *is* `#[track_caller]`, both the vtable and a function pointer created from that method will be `ReifyShim(def_id)`. Currently, the reason is optional to ensure no additional unique `ReifyShim`s are added without KCFI on. However, the case in which an extra `ReifyShim` is created is sufficiently rare that this may be worth revisiting to reduce complexity.		2024-04-02 19:11:16 +00:00
..
src	Track reason for creating a ReifyShim	2024-04-02 19:11:16 +00:00
Cargo.toml	bump itertools to 0.12	2024-03-08 12:34:05 +03:00
messages.ftl	Print list of missing target features when calling a function with target features outside an unsafe block	2023-11-27 19:13:11 +01:00