kurtlawrence / kserd Goto Github PK

Implement some blanket implementations of ToKserd

• Box<T>
• Result<T, E>
• Option<T>
• Tuples out to 16? 12

Create a convenience accessor for container values that can retrieve a value and pattern match it to a particular value. This is useful for asserting a field exists with a certain shape of data.

FormattingConfig could definitely be const, explore other options.

data field = 101

Provides a poor backtrace message. This can be improved by doing the recognising of fields last and cutting if it fails.

Support for multiline strings, both parsing and printing.

This parses fine:

[[list]]
"Hello, world!"

[[list]]
"This is a list"

[[list]]
"as entries"

[key]
    inner-item = "This is a container"
    num = 101
    another = "more words to write stuff"
    byte-array = b91'fdsaljfjdsa'

While this crashes (notice the extra line and \t):

[[list]]
"Hello, world!"

[[list]]
"This is a list"

[[list]]
"as entries"

[key]
    inner-item = "This is a container"
    num = 101
    another = "more words to write stuff"
    byte-array = b91'fdsaljfjdsa'
    

On main page, kserd::format should be kserd::fmt.

All links need checking.

Test the number conversion methods as_u128 and as_i128 as a float value of -1 returns uint of 0.

Use clippy as part of the CI

Parsing of named tuples fails.

• Test and fix parsing of named tuples
• Test and fix parsing of named containers
• Test and fix parsing of named sequences
• Test and fix parsing of named maps

Printing a ZST will not parse back:

struct Foo;
let a = kserd::enc(&Some(Foo)).unwrap();
let kserd = kserd::parse::parse(a.as_str()).unwrap(); // fails

Check with enum types:

enum Foo {
    Bar(String),
    Zog
}

Currently parsing of a verbose kserd layout does not allow to give an id of the container.

Add functionality to supply a name/id

When trying to use Kserd::with_id("adf", Value::new_cntr()?), it should be able to turn InvalidFieldName into a ToKserdErr

This would allow cntrs to be accessed via a &str