The current iteration of faer::polars::polars_to_faer_fxx requires that a slice &[&str] of column names be passed to the function. While there is nothing wrong with this in an absolute sense, it does make for a somewhat awkward workflow when working with polars.
A pattern more aligned to how polars functions is to remove the &[&str] item from the function signature, and have the function create a Mat<E> from the entire frame. The function should also error if columns containing invalid data types (such as strings) are passed in as well.
The current iteration of
faer::polars::polars_to_faer_fxxrequires that a slice&[&str]of column names be passed to the function. While there is nothing wrong with this in an absolute sense, it does make for a somewhat awkward workflow when working withpolars.A pattern more aligned to how
polarsfunctions is to remove the&[&str]item from the function signature, and have the function create aMat<E>from the entire frame. The function should also error if columns containing invalid data types (such as strings) are passed in as well.