Transform feature "ignore-logger-errors" to additive feature.

Author: phip1611

CHANGELOG.md

@@ -15,6 +15,8 @@
   Now you can compare everything that is `AsRef<str>` (such as `String` and `str`
   from the standard library) to uefi strings. Please head to the documentation of
   `EqStrUntilNul` to find out limitations and further information.
+- **Breaking**: renamed feature `ignore-logger-errors` to `panic-on-logger-errors` so that it is
+  additive. It is now a default feature.
 
 ### Changed
 

Cargo.toml

@@ -19,13 +19,14 @@ categories = ["embedded", "no-std", "api-bindings"]
 license = "MPL-2.0"
 
 [features]
-default = []
+default = ["panic-on-logger-errors"]
 alloc = []
 exts = []
 logger = []
 # Ignore text output errors in logger as a workaround for firmware issues that
-# were observed on the VirtualBox UEFI implementation (see uefi-rs#121)
-ignore-logger-errors = []
+# were observed on the VirtualBox UEFI implementation (see uefi-rs#121).
+# In those cases, this feature can be excluded by removing the default features.
+panic-on-logger-errors = []
 
 [dependencies]
 bitflags = "1.3.2"

src/logger.rs

@@ -73,11 +73,11 @@ impl log::Log for Logger {
             // Ignoring errors is bad, especially when they represent loss of
             // precious early-boot system diagnosis data, so we panic by
             // default. But if you experience this problem and want your UEFI
-            // application to keep running when it happens, you can enable the
-            // `ignore-logger-error` cargo feature. If you do so, logging errors
+            // application to keep running when it happens, you can disalbe the
+            // `panic-on-logger-errors` cargo feature. If you do so, logging errors
             // will be ignored by `uefi-rs` instead.
             //
-            if !cfg!(feature = "ignore-logger-errors") {
+            if cfg!(feature = "panic-on-logger-errors") {
                 result.unwrap()
             }
         }