Builtin trace_if_false
#731
KristianBalaj
started this conversation in
Core language features
Replies: 1 comment 1 reply
-
That is a tricky one for sure. The compiler isn't "aware" of custom functions. But we could imagine overloading the builtins with some Aiken builtins which would be entirely gone after the compilation steps. I am not sure whether I like or hate this idea for now 😅 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Coming back with this aiken-lang/stdlib#55
Solution via a library function is not good enough and there should be a language builtin that is properly optimised when traces turned on/off.
The main drawback when using
trace_if_false
as library function is when compiling with traces off, the trace string and the if else remains in the created validator in comparison to the builtin?
operator that optimises the code as it should when traces off.Beta Was this translation helpful? Give feedback.
All reactions