Everywhere: Rename ASSERT => VERIFY

(...and ASSERT_NOT_REACHED => VERIFY_NOT_REACHED)

Since all of these checks are done in release builds as well,
let's rename them to VERIFY to prevent confusion, as everyone is
used to assertions being compiled out in release.

We can introduce a new ASSERT macro that is specifically for debug
checks, but I'm doing this wholesale conversion first since we've
accumulated thousands of these already, and it's not immediately
obvious which ones are suitable for ASSERT.

1 files changed, 3 insertions, 3 deletions

diff --git a/Kernel/Storage/StorageDevice.cpp b/Kernel/Storage/StorageDevice.cpp
index 98b3d08421..2de967e270 100644
--- a/Kernel/Storage/StorageDevice.cpp
+++ b/Kernel/Storage/StorageDevice.cpp
@@ -100,7 +100,7 @@ KResultOr<size_t> StorageDevice::read(FileDescription&, size_t offset, UserOrKer
             return EIO;
         case AsyncDeviceRequest::MemoryFault:
             // This should never happen, we're writing to a kernel buffer!
-            ASSERT_NOT_REACHED();
+            VERIFY_NOT_REACHED();
         default:
             break;
         }
@@ -172,7 +172,7 @@ KResultOr<size_t> StorageDevice::write(FileDescription&, size_t offset, const Us
                 return EIO;
             case AsyncDeviceRequest::MemoryFault:
                 // This should never happen, we're writing to a kernel buffer!
-                ASSERT_NOT_REACHED();
+                VERIFY_NOT_REACHED();
             default:
                 break;
             }
@@ -193,7 +193,7 @@ KResultOr<size_t> StorageDevice::write(FileDescription&, size_t offset, const Us
                 return EIO;
             case AsyncDeviceRequest::MemoryFault:
                 // This should never happen, we're writing to a kernel buffer!
-                ASSERT_NOT_REACHED();
+                VERIFY_NOT_REACHED();
             default:
                 break;
             }