Support for u128, i128 integer types

[AregevDev]

Pretty self-explained, serde is already support them, will be nice to see them in the TOML format

[alexcrichton]

Thanks for the report! Can you gist an example of what doesn't work to have a good test case to check in?

[AregevDev]

Sure thing, will be done when I will be back

[AregevDev]

https://gist.github.com/AregevDev/79dcde42ee06c23d3f5a892596001667
There you go!

[AregevDev]

Any news?

[AregevDev]

I serialized a struct with two 128 bit integers successfully but deserializing them is the tricky part

[AregevDev]

Built from source and modified a little

[AregevDev]

Solved, I can deserialize i/u128 which are not overflowing the i/u64::max_value() perspectively

[nullchinchilla]

I'd like to bump this issue a bit, since it's quite a critical feature for my use case.

[TheDarkula]

I opened a pull request to add this functionality: #445

Unfortunately, I read through the code, and it seems like this would take a good bit of rewriting.
From what I can tell from here and here, all integers are interpreted as an i64, which seems inefficient.

[epage]

Maintenance of this crate has moved to the https://github.com/toml-rs/toml repo. As a heads up, we plan to move toml to be on top of toml_edit, see toml-rs/toml#340.

Closing this out. If this is still a problem, feel free to recreate this issue in the new repo.