diff options
| author | Manish Goregaokar <manishsmail@gmail.com> | 2015-06-04 10:07:02 +0530 |
|---|---|---|
| committer | Manish Goregaokar <manishsmail@gmail.com> | 2015-06-04 10:07:02 +0530 |
| commit | 8c2806caaedc9b83868b14dcaf5f33420be9d368 (patch) | |
| tree | 86886e31280f1458fb2d1466aef3e09865dfb51b /src/test/run-pass/thinlto | |
| parent | 06c6b3caaf5fdd79be11377492547639dc975652 (diff) | |
| parent | babb2684d80aee86ba73ffb1af04617fb2943a06 (diff) | |
| download | rust-8c2806caaedc9b83868b14dcaf5f33420be9d368.tar.gz rust-8c2806caaedc9b83868b14dcaf5f33420be9d368.zip | |
Rollup merge of #25900 - lorenzb:more_about_types, r=nikomatsakis
My main sources of information are [RFC401](https://github.com/rust-lang/rfcs/blob/master/text/0401-coercions.md), the rust IRC channel, and a bunch of experiments to figure out what `rustc` currently supports. Note that the RFC calls for some coercion behaviour that is not implemented yet (see #18469). The documentation in this PR mostly covers current behaviour of rust and doesn't document the future behaviour. I haven't written about receiver expression coercion. I would be happy to rewrite/adapt the PR according to feedback. r? @steveklabnik
Diffstat (limited to 'src/test/run-pass/thinlto')
0 files changed, 0 insertions, 0 deletions