-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
feature request: please add support for Result<T, E>
to IntoExcelData
#64
Comments
I'm not, at first glance, convinced of the general utility of this. However, I'll consider it and if anyone else thinks this would be useful then a +1 or "me too" comment will help persuade me. |
Add support for handling Result<T, E> values in the write() method. Feature request #64
Ok. It seems like you have a plan you are working to. I've added this to main. Let me know how you get on.
|
Add support for handling Result<T, E> values in the write() method. Feature request #64
Thanks @jmcnamara , yes I will let you know if this feature can be added to |
This feature has been pushed to crates.io in |
Feature Request
Currently
IntoExcelData
supportsOption<T>
, which can be used when a value maybe present or not. However often when dealing with tabular data we need to define fallback types, for instance a column could normally contain anf64
but may sometimes contain aString
. I think the best way to deal with this very common occurrence is to useResult<f64, String>
. Of course also other use cases can be envisioned for aResult<T, E>
type.The
rust_xlsxwriter::Worksheet::write*
methods should correctly writeResult<T, E>
if bothT
andE
are supported types.The text was updated successfully, but these errors were encountered: