diff options
| author | bors <bors@rust-lang.org> | 2022-09-21 04:35:20 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-09-21 04:35:20 +0000 |
| commit | 1de00d1ac5247a02184ef7ad044f6521ade7e0cc (patch) | |
| tree | be6674f67c6533ebea19374e66c386592af8289b /compiler/rustc_ty_utils/src/errors.rs | |
| parent | 4ecfdfac51b159f68fce608792affb34a70e6f73 (diff) | |
| parent | 3b573c9b986a98064b6c155c7029f8ce253ed69c (diff) | |
| download | rust-1de00d1ac5247a02184ef7ad044f6521ade7e0cc.tar.gz rust-1de00d1ac5247a02184ef7ad044f6521ade7e0cc.zip | |
Auto merge of #100096 - compiler-errors:fn-return-must-be-sized, r=jackh726
a fn pointer doesn't implement `Fn`/`FnMut`/`FnOnce` if its return type isn't sized I stumbled upon #83915 which hasn't received much attention recently, and I wanted to revive it since this is one existing soundness hole that seems pretty easy to fix. I'm not actually sure that the [alternative approach described here](https://github.com/rust-lang/rust/pull/83915#issuecomment-823643322) is sufficient, given the `src/test/ui/function-pointer/unsized-ret.rs` example I provided below. Rebasing the branch mentioned in that comment and testing that UI test, it seems that we actually end up only observing that `str: !Sized` during monomorphization, whereupon we ICE. Even if we were to fix that ICE, ideally we'd be raising an error that a fn pointer is being used badly during _typecheck_ instead of monomorphization, hence adapting the original approach in #83915. I am happy to close this if people would prefer we rebase the original PR and land that -- I am partly opening to be annoying and get people thinking about this unsoundness again :heart: :smile_cat: cc: `@estebank` and `@nikomatsakis` r? types Here's a link to the thread: https://rust-lang.zulipchat.com/#narrow/stream/144729-t-types/topic/PR.20.2383915/near/235421351 for more context.
Diffstat (limited to 'compiler/rustc_ty_utils/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
