Lower revert argument

crates/lowering/src/mappers/functions.rs

@@ -221,7 +221,9 @@ fn func_stmt(context: &mut FnContext, stmt: Node<fe::FuncStmt>) -> Vec<Node<fe::
         fe::FuncStmt::Pass => vec![stmt.kind],
         fe::FuncStmt::Break => vec![stmt.kind],
         fe::FuncStmt::Continue => vec![stmt.kind],
-        fe::FuncStmt::Revert { .. } => vec![stmt.kind],
+        fe::FuncStmt::Revert { error } => vec![fe::FuncStmt::Revert {
+            error: error.map(|expr| expressions::expr(context, expr)),
+        }],
     };
     let span = stmt.span;
 

crates/test-files/fixtures/crashes/revert_const.fe

@@ -0,0 +1,7 @@
+const FOO: u256 = 0x101
+
+struct Error:
+  code: u256
+
+fn exit():
+  revert Error(code = FOO)

crates/tests/src/crashes.rs

@@ -18,3 +18,4 @@ macro_rules! test_file {
 
 test_file! { agroce531 }
 test_file! { agroce550 }
+test_file! { revert_const }

newsfragments/619.bugfix.md

@@ -0,0 +1,13 @@
+The argument to `revert` wasn't being lowered by the compiler,
+meaning that some `revert` calls would cause a compiler panic
+in later stages. For example:
+
+```
+const BAD_MOJO: u256 = 0xdeaddead
+
+struct Error:
+  code: u256
+
+fn fail():
+  revert Error(code = BAD_MOJO)
+```