Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development tracking of roadmap progress #9

Open
naturallymitchell opened this issue Sep 30, 2018 · 6 comments
Open

Development tracking of roadmap progress #9

naturallymitchell opened this issue Sep 30, 2018 · 6 comments

Comments

@naturallymitchell
Copy link

naturallymitchell commented Sep 30, 2018

How close is this to usable? I don't care about some incompleteness and API changes, since I'm making alpha software anyway. So switching formats and parsers later is no issue. But I still want to get a sense for where we're at with it.

It seems like the best available Rust parser for structured data. yaml-rust doesn't support StrictYAML chyh1990/yaml-rust#102 , and TOML has negative reviews, eg getzola/zola#317

I want to use it for configuration, log files, and content headers.

@Keats
Copy link
Owner

Keats commented Sep 30, 2018

I want to use it for configuration, log files, and content headers.

SCL is only meant for configuration, i don't think it would make sense for logging/content header where. JSON seems to be a better for logging if you want to pass data around.

There are a few important things:

@naturallymitchell
Copy link
Author

Will you possibly create the serde-scl crate before the final spec? This would give a chance to get real world test cases for discussion.

@Keats
Copy link
Owner

Keats commented Oct 5, 2018

I'm not sure I will have the time soon but it shouldn't be too hard to do since we only want the deserialization and the parser already exists

@naturallymitchell
Copy link
Author

naturallymitchell commented Nov 13, 2018

@Keats any word on serde-scl?

(sorry for nudging)

@Keats
Copy link
Owner

Keats commented Nov 14, 2018

None yet, focusing on gutenberg 0.5, then tera 1.0 and then I'll have a look at scl. It should be fairly easy for someone to write it though - the parser already exists and we only care about getting it from a file to a struct

@naturallymitchell
Copy link
Author

@Keats any word on when you intend to revisit SCL and how much you'll be able to focus on it?


We didn't make serde-scl, but we have rlua-scl, which still needs to be factored out: https://github.com/foundpatterns/torchbear/blob/master/src/bindings/text/scl.rs


If you could hop on Discord, that'd be great. Rust, in general, seems to be moving that way: https://discordapp.com/invite/rust-lang . Perhaps we could organize an SCL meetup and get done within one hour through voice what would take weeks or months to do asynchronously in issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants