Panic Handler: Switch to `error!`?

[phip1611]

We might want to switch to error!() from println() or make this configurable in our panic_handler (uefi crate feature)? often when things go wrong? At least in one of my examples, I didn't actually get printed messages at all. Using error!() helped me at least to get log o the debugcon device.

[nytpu]

Yeah, I agree, was just about to file my own issue that once one initializes graphics (or anything else that disables console output), one can't get panic messages with the default panic handler.

Maybe it should write to the logger (or directly to debugcon if logging isn't available but debugcon is) alongside println? Or just fall back to println if logging isn't available?

[phip1611]

I'm not entirely certain what the ideal approach is. I'm also unsure whether the default logger can realistically be generic enough to cover every possible use case.. or if it is better for users to just provide their own