rust/src/test/ui/consts/const-blocks/fn-call-in-non-const.stderr

error[E0277]: the trait bound `Option<Bar>: Copy` is not satisfied
  --> $DIR/fn-call-in-non-const.rs:14:31
   |
LL |     let _: [Option<Bar>; 2] = [no_copy(); 2];
   |                               ^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `Option<Bar>`
   |
   = help: the following implementations were found:
             <Option<T> as Copy>
   = note: the `Copy` trait is required because the repeated element will be copied
   = help: consider creating a new `const` item and initializing with the result of the function call to be used in the repeat position, like `const VAL: Type = const_fn();` and `let x = [VAL; 42];`
   = help: create an inline `const` block, see PR #2920 <https://github.com/rust-lang/rfcs/pull/2920> for more information

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 02:40:56 -05:00			error[E0277]: the trait bound `Option<Bar>: Copy` is not satisfied
Remove const_in_array_rep_expr 2021-01-26 16:49:30 -06:00			`--> $DIR/fn-call-in-non-const.rs:14:31`
tests: Add tests that use const fns. 2019-06-13 11:30:49 -05:00			`\|`
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. 2019-11-22 12:45:49 -06:00			`LL \| let _: [Option<Bar>; 2] = [no_copy(); 2];`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 02:40:56 -05:00			\| ^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `Option<Bar>`
tests: Add tests that use const fns. 2019-06-13 11:30:49 -05:00			`\|`
			`= help: the following implementations were found:`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 02:40:56 -05:00			`<Option<T> as Copy>`
tests: Add tests that use const fns. 2019-06-13 11:30:49 -05:00			= note: the `Copy` trait is required because the repeated element will be copied
update message 2021-02-13 22:38:37 -06:00			= help: consider creating a new `const` item and initializing with the result of the function call to be used in the repeat position, like `const VAL: Type = const_fn();` and `let x = [VAL; 42];`
added a suggestion to create a `const` item if the `fn` in the array repeat expression is a `const fn` 2021-01-29 00:24:19 -06:00			= help: create an inline `const` block, see PR #2920 <https://github.com/rust-lang/rfcs/pull/2920> for more information
tests: Add tests that use const fns. 2019-06-13 11:30:49 -05:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0277`.