Re: [PATCH 4/4] panic_qr: use new #[export] macro

2025-02-28 Thread Andreas Hindborg
"Alice Ryhl" writes: > This validates at compile time that the signatures match what is in the > header file. It highlights one annoyance with the compile-time check, > which is that it can only be used with functions marked unsafe. It would indeed be nice if there was a way to mark some functio

Re: [PATCH 4/4] panic_qr: use new #[export] macro

2025-02-27 Thread Alice Ryhl
On Thu, Feb 27, 2025 at 10:29 PM Boqun Feng wrote: > > On Thu, Feb 27, 2025 at 05:02:02PM +, Alice Ryhl wrote: > > This validates at compile time that the signatures match what is in the > > header file. It highlights one annoyance with the compile-time check, > > which is that it can only be

Re: [PATCH 4/4] panic_qr: use new #[export] macro

2025-02-27 Thread Boqun Feng
On Thu, Feb 27, 2025 at 05:02:02PM +, Alice Ryhl wrote: > This validates at compile time that the signatures match what is in the > header file. It highlights one annoyance with the compile-time check, > which is that it can only be used with functions marked unsafe. > > If the function is not

[PATCH 4/4] panic_qr: use new #[export] macro

2025-02-27 Thread Alice Ryhl
This validates at compile time that the signatures match what is in the header file. It highlights one annoyance with the compile-time check, which is that it can only be used with functions marked unsafe. If the function is not unsafe, then this error is emitted: error[E0308]: `if` and `else` ha