5 Commits

Author	SHA1	Message	Date
Bryan Garza	f4cf8f65a5	Safe Transmute: Refactor error handling and Answer type ... - Create `Answer` type that is not just a type alias of `Result` - Remove a usage of `map_layouts` to make the code easier to read - Don't hide errors related to Unknown Layout when computing transmutability	2023-06-12 16:56:21 -07:00
Bryan Garza	263a4f2cb6	Safe Transmute: Change Answer type to Result ... This patch updates the `Answer` type from `rustc_transmute` so that it just a type alias to `Result`. This makes it so that the standard methods for `Result` can be used to process the `Answer` tree, including being able to make use of the `?` operator on `Answer`s. Also, remove some unused functions	2023-05-24 14:52:19 -07:00
Bryan Garza	36febe1f4d	Improve safe transmute error reporting ... This patch updates the error reporting when Safe Transmute is not possible between 2 types by including the reason. Also, fix some small bugs that occur when computing the `Answer` for transmutability.	2023-04-13 21:57:08 +00:00
Jack Wrenn	f46fffc276	safe transmute: use Assume struct to provide analysis options ... This was left as a TODO in #92268, and brings the trait more in line with what was defined in MCP411. `Assume::visibility` has been renamed to `Assume::safety`, as library safety is what's actually being assumed; visibility is just the mechanism by which it is currently checked (this may change). ref: https://github.com/rust-lang/compiler-team/issues/411 ref: https://github.com/rust-lang/rust/issues/99571	2022-08-22 18:37:54 +00:00
Jack Wrenn	bc4a1dea41	Initial (incomplete) implementation of transmutability trait. ... This initial implementation handles transmutations between types with specified layouts, except when references are involved. Co-authored-by: Igor null <m1el.2027@gmail.com>	2022-07-27 17:33:56 +00:00