Comments (3)
zslayton
commented on August 16, 2024
The practical effect of this change will be that Element::read_* and Element::write_* methods will be able to accept a ReadConfig and WriteConfig respectively, allowing users to (e.g.) specify a Catalog or request a particular version of Ion. These types also future-proof these methods by giving us an avenue by which to add more options without modifying the API.
from ion-rust.
popematt
commented on August 16, 2024
If we remove the feature gate for Encoding, then we need to add a feature gate specifically to the Ion 1.1 encodings (until the Ion 1.1 spec is finalized). Currently, the Cargo.toml file does not list any feature for Ion 1.1.
from ion-rust.
zslayton
commented on August 16, 2024
Interestingly, I've learned that it's possible to expose a type that's generic over E: Encoding without making Encoding itself pub, which is nice. This is currently the case with WriteConfig<E: Encoding>. In light of that, I'm closing this for now. If anyone disagrees, please re-open this and we'll discuss.
from ion-rust.
Related Issues (20)
- Remove automatic IVM writing from raw writers?
- Add text reader support for iterating through incomplete/invalid containers
- Should ValueRef container types implement PartialEq?
- Add support for half-precision floats in binary 1.1 reader. HOT 1
- Panic when using `format!` and debug output for a nested value with a bad escape character in the LazyReader.
- Wire up `Catalog` in `SystemReader` HOT 1
- Give users a way to implement `IonInput` for their own types
- [serde] Implement is_human_readable on (de)serializer HOT 3
- Add support for getting the encoding from `LazyValue`
- Miri tests failure
- Define an MSRV policy for the crate HOT 3
- Convert serde_json::Value to Ion HOT 5
- Derive `opcode_length` instead of setting it explicitly HOT 1
- Verify that parameter names have at most one annotation (i.e. the encoding)
- Refer to constant for unit tests defining user macros HOT 1
- Add e-exp call to `(:annotate ..)` to unit tests
- It seems `Position` is not publicly nameable
- Difficulty accessing `Span` from `Lazy*` types.
- `List` and `Sexp` should implement `FromIterator<Element>`
- Container writers panic if early return prevents `close()`
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ion-rust.