Open nekketsuuu opened 6 years ago
To tell the truth, I have noticed the problem for a long time… It is mainly due to the implementation of the translation of manually written types to internal types (see here).
So this is a kind of bug. Thanks for letting me know that. I'll change my type's name to differ from primitives as a workaround for the time being.
I noticed that the following code produces an odd error.
This behavior may be related to the specification of shadowing of types. SATySFi can shadow user-defined types as follows. But can we shadow primitive types?
Note that OCaml can shadow primitive types.