]> git.lizzy.rs Git - rust.git/commit
projects / rust.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 53712f8) | patch
Fix tests for RFC 2203 in a `const`
authorDylan MacKenzie <ecstaticmorse@gmail.com>
Fri, 22 Nov 2019 18:45:49 +0000 (10:45 -0800)
committerDylan MacKenzie <ecstaticmorse@gmail.com>
Fri, 22 Nov 2019 19:01:31 +0000 (11:01 -0800)
commitfcf4bee7d3d69356a9eb702f9e0a9ddba238d33f
tree55c85d4cef0c4295f5e73960a25e03f2e02080e4tree | snapshot
parent53712f8637dbe326df569a90814aae1cc5429710commit | diff
Fix tests for RFC 2203 in a `const`

The previous test was incorrect. `const fn`s are *always* promotable
when inside a `const`, so it should pass. The error was caused by a bug
in `promote_consts`. I've added a failing test outside a `const`
alongside the existing one, which is now run-pass.
src/test/ui/consts/rfc-2203-const-array-repeat-exprs/const-fns.rs [deleted file] blob | history
src/test/ui/consts/rfc-2203-const-array-repeat-exprs/const-fns.stderr [deleted file] blob | history
src/test/ui/consts/rfc-2203-const-array-repeat-exprs/fn-call-in-const.rs [new file with mode: 0644] blob
src/test/ui/consts/rfc-2203-const-array-repeat-exprs/fn-call-in-non-const.rs [new file with mode: 0644] blob
src/test/ui/consts/rfc-2203-const-array-repeat-exprs/fn-call-in-non-const.stderr [new file with mode: 0644] blob
Empowering everyone to build reliable and efficient software.