rooooooooob
rooooooooob
```cddl basic = (text, uint) choice = [ ; @name foo basic // ; @name bar uint, basic ] ``` will generate `Self::Foo(Foo::new(...))` instead of `Self::Foo(Basic::new(...))` which won't compile as...
```cddl hash = bytes .size (0..8) non_overlap_basic_embed = [ ; @name identity tag: 0 // ; @name hash tag: 1, hash: bytes .size 32 ] ``` This should be fine...
CDDL: ```cddl bool_wrapper = bool ; @newtype ``` Compile error: ``` 116 | Ok(Self(raw.bool().map_err(Into::into)?)) | ^^^^^^^^^^ cannot infer type of the type parameter `T` declared on the trait `Into` ```
``` foo = [ single: [uint] ] ``` is treated as: ``` foo = [ single: [* uint] ] ``` As per the CDDL RFC: >If no occurrence indicator is...
Low priority but here to document. e.g.: ```cddl foo = [ ? x: 1, y: uint, ] ```
```cddl foo = 0.1 .. 0.5 bar = f64 .le 3.1415926535 ``` low priority issue, just made to keep documentation on unsupported things and to link in the panic
e.g. ```cddl foo = 1..7 ``` We only support these integer bounds when they map to existing rust primitives e.g. `uint .le 255` turns to `u8`, etc. Questions: 1. Do...
e.g. general (n to m elements) bounds on arrays: ```cddl foo = [n*m uint] ``` We already have support for the following cases: * `[* uint]` (0 or more i.e....
```cddl foo = uint .size 2 ; @newtype ``` Will not work, and will instead generate a type alias as if the @newtype wasn't there. The parsing logic in general...
Certain types (e.g. basic groups embedded in map structs, or array structs with optional fields) don't implement deserialization. The wasm wrappers don't seem to be aware of this and will...