about summary refs log tree commit diff
path: root/src/test/codegen/src-hash-algorithm
diff options
context:
space:
mode:
authorMara Bos <m-ou.se@m-ou.se>2020-11-16 17:26:13 +0100
committerGitHub <noreply@github.com>2020-11-16 17:26:13 +0100
commitde0aa6169f0c7abbc8aa4d7e735f5da57a1e65ab (patch)
treef6bef1fbd59655adb14a0e5986d1906c38569afc /src/test/codegen/src-hash-algorithm
parent4cdd22062580b46cbb6cf97ca56d59ebeb1e91b7 (diff)
parent6728240f36c7dd1ecb16d396c9c61933d2f01da9 (diff)
downloadrust-de0aa6169f0c7abbc8aa4d7e735f5da57a1e65ab.tar.gz
rust-de0aa6169f0c7abbc8aa4d7e735f5da57a1e65ab.zip
Rollup merge of #76339 - CDirkx:structural-match-range, r=Mark-Simulacrum
Test structural matching for all range types

As of #70166 all range types (`core::ops::Range` etc.) can be structurally matched upon, and by extension used in const generics. In reference to the fact that this is a publicly observable property of these types, and thus falls under the Rust stability guarantees of the standard library, a regression test was added in #70283.

This regression test was implemented by me by testing for the ability to use the range types within const generics, but that is not the actual property the std guarantees now (const generics is still unstable). This PR addresses that situation by adding extra tests for the range types that directly test whether they can be structurally matched upon.

Note: also adds the otherwise unrelated test `test_range_to_inclusive` for completeness with the other range unit tests
Diffstat (limited to 'src/test/codegen/src-hash-algorithm')
0 files changed, 0 insertions, 0 deletions