and people complain about wayland.

The Idea is that the enum acts as a union, capable of holding any of the member types, It’s not that different from using identifiers and when transpiling to rust I will probably only support variants beginning with string literals (or maybe generate them).

The main reason is that I could use type inference to define the variants in a returned anonymous enum.

I like the pipe symbol because it is useful for distinguishing between enums and structs without keywords. And I just personally think it looks better. And allow for pretty anonymous enums like (|String |Int) for something that can accept both a string and an integer.

Not having a license is “All Rights Reserved”. That’s why I bothered with the license section in the readme at all.

Thanks!

I intend for the language to have a similar borrow checker and type system. Which is why I’m targeting rust. It means I have something to check against when writing the tooling. (Although I’m not sure I’ll get that far. My computer is littered with dead projects).

I don’t really want to clutter the repo with something so frivolous. If they were links or an SPDX ID would that be enough?

I’m intending to use this for a custom language “OA” that I want to compile to Rust and JS to start with.

I don’t know enough about LLVM to compile directly to machine code although I would like to.

You can use Unicode pictures: ␜ ␝ ␞ ␟

https://en.wikipedia.org/wiki/Control_Pictures