rust/tests/ui/alloc-error/alloc-error-handler-bad-signature-3.stderr

error[E0061]: this function takes 0 arguments but 1 argument was supplied
  --> $DIR/alloc-error-handler-bad-signature-3.rs:10:1
   |
LL |   #[alloc_error_handler]
   |   ---------------------- in this procedural macro expansion
LL |   fn oom() -> ! {
   |  _-^^^^^^^^^^^^
LL | |     loop {}
LL | | }
   | |_- argument of type `core::alloc::Layout` unexpected
   |
note: function defined here
  --> $DIR/alloc-error-handler-bad-signature-3.rs:10:4
   |
LL | fn oom() -> ! {
   |    ^^^
   = note: this error originates in the attribute macro `alloc_error_handler` (in Nightly builds, run with -Z macro-backtrace for more info)
help: remove the extra argument
   |
LL | fn oom() -> !() {
   |              ++

error: aborting due to previous error

For more information about this error, try `rustc --explain E0061`.
Rewrite implementation of `#[alloc_error_handler]` The new implementation doesn't use weak lang items and instead changes `#[alloc_error_handler]` to an attribute macro just like `#[global_allocator]`. The attribute will generate the `__rg_oom` function which is called by the compiler-generated `__rust_alloc_error_handler`. If no `__rg_oom` function is defined in any crate then the compiler shim will call `__rdl_oom` in the alloc crate which will simply panic. This also fixes link errors with `-C link-dead-code` with `default_alloc_error_handler`: `__rg_oom` was previously defined in the alloc crate and would attempt to reference the `oom` lang item, even if it didn't exist. This worked as long as `__rg_oom` was excluded from linking since it was not called. This is a prerequisite for the stabilization of `default_alloc_error_handler` (#102318). 2022-10-13 20:24:58 -05:00			`error[E0061]: this function takes 0 arguments but 1 argument was supplied`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/alloc-error-handler-bad-signature-3.rs:10:1`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Rewrite implementation of `#[alloc_error_handler]` The new implementation doesn't use weak lang items and instead changes `#[alloc_error_handler]` to an attribute macro just like `#[global_allocator]`. The attribute will generate the `__rg_oom` function which is called by the compiler-generated `__rust_alloc_error_handler`. If no `__rg_oom` function is defined in any crate then the compiler shim will call `__rdl_oom` in the alloc crate which will simply panic. This also fixes link errors with `-C link-dead-code` with `default_alloc_error_handler`: `__rg_oom` was previously defined in the alloc crate and would attempt to reference the `oom` lang item, even if it didn't exist. This worked as long as `__rg_oom` was excluded from linking since it was not called. This is a prerequisite for the stabilization of `default_alloc_error_handler` (#102318). 2022-10-13 20:24:58 -05:00			`LL \| #[alloc_error_handler]`
			`\| ---------------------- in this procedural macro expansion`
			`LL \| fn oom() -> ! {`
			`\| _-^^^^^^^^^^^^`
			`LL \| \| loop {}`
			`LL \| \| }`
			\| \|_- argument of type `core::alloc::Layout` unexpected
			`\|`
			`note: function defined here`
			`--> $DIR/alloc-error-handler-bad-signature-3.rs:10:4`
			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| fn oom() -> ! {`
Rewrite implementation of `#[alloc_error_handler]` The new implementation doesn't use weak lang items and instead changes `#[alloc_error_handler]` to an attribute macro just like `#[global_allocator]`. The attribute will generate the `__rg_oom` function which is called by the compiler-generated `__rust_alloc_error_handler`. If no `__rg_oom` function is defined in any crate then the compiler shim will call `__rdl_oom` in the alloc crate which will simply panic. This also fixes link errors with `-C link-dead-code` with `default_alloc_error_handler`: `__rg_oom` was previously defined in the alloc crate and would attempt to reference the `oom` lang item, even if it didn't exist. This worked as long as `__rg_oom` was excluded from linking since it was not called. This is a prerequisite for the stabilization of `default_alloc_error_handler` (#102318). 2022-10-13 20:24:58 -05:00			`\| ^^^`
			= note: this error originates in the attribute macro `alloc_error_handler` (in Nightly builds, run with -Z macro-backtrace for more info)
			`help: remove the extra argument`
			`\|`
			`LL \| fn oom() -> !() {`
			`\| ++`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			`error: aborting due to previous error`

Rewrite implementation of `#[alloc_error_handler]` The new implementation doesn't use weak lang items and instead changes `#[alloc_error_handler]` to an attribute macro just like `#[global_allocator]`. The attribute will generate the `__rg_oom` function which is called by the compiler-generated `__rust_alloc_error_handler`. If no `__rg_oom` function is defined in any crate then the compiler shim will call `__rdl_oom` in the alloc crate which will simply panic. This also fixes link errors with `-C link-dead-code` with `default_alloc_error_handler`: `__rg_oom` was previously defined in the alloc crate and would attempt to reference the `oom` lang item, even if it didn't exist. This worked as long as `__rg_oom` was excluded from linking since it was not called. This is a prerequisite for the stabilization of `default_alloc_error_handler` (#102318). 2022-10-13 20:24:58 -05:00			For more information about this error, try `rustc --explain E0061`.