diff options
| author | bors <bors@rust-lang.org> | 2016-08-03 22:56:33 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-08-03 22:56:33 -0700 |
| commit | 271d048523b6c1b0e773d9e5cc76bbb997cc180c (patch) | |
| tree | d7350e864daae060588a674a6180cc8d41e2c63e /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 40f3ee2a01ef24d57430726c098de905c7c6e04a (diff) | |
| parent | 5c88efc0da9d5222965fe8eaeb1bf48897da7ec1 (diff) | |
| download | rust-271d048523b6c1b0e773d9e5cc76bbb997cc180c.tar.gz rust-271d048523b6c1b0e773d9e5cc76bbb997cc180c.zip | |
Auto merge of #35015 - petrochenkov:forearg, r=nikomatsakis
Properly enforce the "patterns aren't allowed in foreign functions" rule Cases like `arg @ PATTERN` or `mut arg` were missing. Apply the same rule to function pointer types. Closes https://github.com/rust-lang/rust/issues/35203 [breaking-change], no breakage in sane code is expected though r? @nikomatsakis This is somewhat related to https://github.com/rust-lang/rfcs/pull/1685 (cc @matklad). The goal is to eventually support full pattern syntax where it makes sense (function body may present) and to support *only* the following forms - `TYPE`, `ident: TYPE`, `_: TYPE` - where patterns don't make sense (function body doesn't present), i.e. in foreign functions and function pointer types.
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions