muon-data / muon Goto Github PK

When the muon file has error, the error reuslt showing to user like this: Error: FailedParse(ExpectedInt), but can't locate which line has error.

This would include Rust-style enums (or C-Style union + tag):

:::
character: choice
  Person: list text
  Animal: text
  Spirit: int
:::
character:
  Person: multiple text
character:
  Animal: fox
character:
  Spirit: 5

For C-Style enums, an type in schema can be omitted and shortcut could be used:

:::
switch_a: choice Direction
  Forward
  Neutral
  Backward
switch_b: choice Direction
:::
switch_a: Neutral
switch_b: Forward

You can also mix variants with associated data with ones that don't have any:

:::
thing: list choice
  None
  Red: record
    value: int
    name: text
  Blue: int
  Nothing
:::
thing: None
thing:
  Red: 10
    name: Bright
thing: Nothing
thing:
  Blue: 25

@DougLau thoughts?

edit: Rename union to choice, add mixed associated data and without associated data example.

I'm thinking adding repositories to this organization for:

• muon-c
• muon-py (Python)
• muon-java
• muon-js (Javascript)
• muon-go
• muon-dart
• muon-kt (Kotlin)

To cover some of the more popular ones. It might be cool to do bindings to muon-rs, but I'm unsure of how that would work with serde (maybe an alternate C API crate?).

A decision needs to be made on how to handle them.

• Int types could have valid ranges or values, like ASN.1
• Text could have maximum (or even minimum?) lengths
• Number could have ranges, or restricted to real values (no NaN/Inf)
• Lists could have length limits