#enum color! [a b c]
-= Red/System Compiler =-
Compiling tests/mytest.reds ...
*** Compilation Error: type mismatch on setting path: char/1
*** expected: [byte!]
*** found: [integer!]
*** in file: %runtime/utils.reds
*** in function: prin-byte
*** at line: 30
*** near: [
I frankly don't understand where the prin-byte comes in during compilation?
print is a variadic function that calls _print which itself calls prin-byte. Square brackets around variadic function's arguments can be omitted if there is a single argument.
But why does the compiler reference a path-assignment, and a function that is not even directly called from the soure?
Looks like a compiler bug, probably a clash between the enumeration symbol c and the local variable c from prin-byte.
FIX: issue #290 (Strange error when trying to compile an #enum)
TESTS: added regression tests for issues #290 and #293.