| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-05-27 | Use more detailed spans in dyn compat errors within bodies | Oli Scherer | -2/+2 | |
| 2025-05-26 | Deduplicate dyn compatibility violations due to coercion | Michael Goulet | -21/+1 | |
| 2025-01-26 | Compiler: Finalize dyn compatibility renaming | León Orell Valerian Liehr | -2/+2 | |
| 2025-01-22 | Refactor dyn-compatibility error and suggestions | Taylor Cramer | -10/+12 | |
| This CL makes a number of small changes to dyn compatibility errors: - "object safety" has been renamed to "dyn-compatibility" throughout - "Convert to enum" suggestions are no longer generated when there exists a type-generic impl of the trait or an impl for `dyn OtherTrait` - Several error messages are reorganized for user readability Additionally, the dyn compatibility error creation code has been split out into functions. cc #132713 cc #133267 | ||||
| 2024-09-25 | Compiler: Rename "object safe" to "dyn compatible" | León Orell Valerian Liehr | -2/+2 | |
| 2023-10-29 | On object safety error, mention new enum as alternative | Esteban Küber | -0/+2 | |
| When we encounter a `dyn Trait` that isn't object safe, look for its implementors. If there's one, mention using it directly If there are less than 9, mention the possibility of creating a new enum and using that instead. Account for object unsafe `impl Trait on dyn Trait {}`. Make a distinction between public and sealed traits. Fix #80194. | ||||
| 2023-05-12 | Note base types of coercion | Michael Goulet | -8/+1 | |
| 2023-01-24 | add feature gate tests for DispatchFromDyn | dimi | -0/+45 | |
