Comments (5)
You can still use Describe if you declare an intermediate struct holding the parameters.
from json.
On second thought, isn't
MyClass{json.at("superint1").to<int>(),
json.at("superint2").to<int>(),
json.at("superbool").to<bool>(),
json.at("superstring").to<std::string>(),
json.at("supervectorofint").to<std::vector<int>>()}
possible to write today as
MyClass{
value_to<int>(json.at("superint1")),
value_to<int>(json.at("superint2")),
value_to<bool>(json.at("superbool")),
value_to<std::string>(json.at("superstring")),
value_to<std::vector<int>>(json.at("supervectorofint"))
}
?
from json.
It is. I think, @kiwixz considers that syntax too cumbersome.
To be honest, I'm not fond of adding just another way to call value_to
.
from json.
I didn't think of using namespace
here which helps a lot.
It still feels weird to me to use it as a free function, especially when we have to_number
as a member.
from json.
True, but making an equivalent of value_to
member function of value
is much more intrusive.
from json.
Related Issues (20)
- Exception of segment fail when run value_from for tree structuor HOT 2
- boost::json::value_to on std::bitset? HOT 6
- Regression: serializing vector<> of objects HOT 4
- Linux gcc compilation failures with --pedantic-errors flag: error: extra ‘;’ HOT 1
- Value Iteration HOT 5
- Question: how to determine the required size for temp buffers? HOT 7
- If an unsigned integer is serialized, deserializing back to the unsigned integer fails HOT 8
- Comment Only: Logo HOT 3
- Stack exaustion while value_from(std::filesystem::path) HOT 5
- Small help for non eagle eyed people HOT 2
- Documentation inconsistency about exceptions HOT 2
- boost::json::value::is_uint64() behaves unintuitively HOT 6
- Add support to universal tag_invoke for class as struct with macro BOOST_DESCRIBE_CLASS HOT 10
- Unable to extract boolean value in numberic format HOT 1
- Add a shorthand to masquerade a type parsing/serializing HOT 1
- Allow unknown described class members with a parse option HOT 5
- Null-dereference warning in value_to HOT 2
- Error in parse_into() Error: unknown name or Error: incomplete JSON HOT 2
- Backwards compatibility? (new structure definitions but old json serialization) HOT 17
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 json.