aboutsummaryrefslogtreecommitdiff
path: root/src/exact_value.cpp
diff options
context:
space:
mode:
authorGinger Bill <bill@gingerbill.org>2016-09-19 21:33:52 +0100
committerGinger Bill <bill@gingerbill.org>2016-09-19 21:33:52 +0100
commit9561dc33cef4c5881034d429524a0498331a740e (patch)
tree23820f1575123ad38d0ecdfa5bad9d8fecf92629 /src/exact_value.cpp
parentbbc9739f5c1f6fa4dc8ad36aed7bcb1cba2eadea (diff)
enum_to_string
Diffstat (limited to 'src/exact_value.cpp')
-rw-r--r--src/exact_value.cpp6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/exact_value.cpp b/src/exact_value.cpp
index 44e291af0..7e0292a09 100644
--- a/src/exact_value.cpp
+++ b/src/exact_value.cpp
@@ -190,7 +190,7 @@ ExactValue exact_unary_operator_value(Token op, ExactValue v, i32 precision) {
}
failure:
- GB_PANIC("Invalid unary operation, %.*s", LIT(token_strings[op.kind]));
+ compiler_error("Invalid unary operation, %.*s", LIT(token_strings[op.kind]));
ExactValue error_value = {};
return error_value;
@@ -212,7 +212,7 @@ i32 exact_value_order(ExactValue v) {
return 4;
default:
- GB_PANIC("How'd you get here? Invalid Value.kind");
+ compiler_error("How'd you get here? Invalid Value.kind");
return -1;
}
}
@@ -249,7 +249,7 @@ void match_exact_values(ExactValue *x, ExactValue *y) {
break;
}
- GB_PANIC("How'd you get here? Invalid ExactValueKind");
+ compiler_error("How'd you get here? Invalid ExactValueKind");
}
// TODO(bill): Allow for pointer arithmetic? Or are pointer slices good enough?