Amando
Amando
> [package-lock.json](https://github.com/rust-lang/libs-team/files/14627185/package-lock.json) What is this? Is it relevant?
@kennytm all valid points. Is there anyone else worth checking with? I can close the issue if not.
For example, something like the example in the Polars docs [here](https://docs.pola.rs/user-guide/expressions/casting/#dates): ```rust use chrono::prelude::*; let date = polars::time::date_range( "date", NaiveDate::from_ymd_opt(2022, 1, 1) .unwrap() .and_hms_opt(0, 0, 0) .unwrap(), NaiveDate::from_ymd_opt(2022, 1, 5)...
Any thoughts on this ?
To be more precise, I would like to do something like: ```rust use time::macros::{date, datetime}; let df: DataFrame = df!( "date" => &[ date!(2020-01-01), date!(2021-01-01), date!(2022-01-01) ], "datetime" => &[...
Any updates on this ?
Yes I've wanted to use the `num-traits` for a while, especially for the `Variable` type in the `autodiff` module, but that seems difficult or impossible currently. If you want to...
Hi @joaquinbejar, thanks for the interest! Which part are you keen to work on? The foundational stuff (time/date, schedules, etc) or the higher level pricing stuff ?
Sure :) take a look at what is already implemented for an idea of what needs to be done. Thanks for your interest !
In order to implement the pricers in a meaningful/useful way, we need the foundational stuff. In particular a decent amount of work is needed in the `time` module, and we...