This PR addresses small issues in string formatting.
[Windows] when dynamically compiling Rust code, the build directory was displayed to the user using backslashes (likes C:\path\to\temp\dir). However, by convention we use forward slashes everywhere, so I changed it to be consistent with all other displayed paths. Forward slash notation allows to copy-paste paths as is, backslashes are treated as escapes sequences and often require additional escaping.
[Follow up to #125] A function in rust_eval_deparse() was previously declared to please R CMD check, but is no longer used. I missed this yesterday when pushed PR. It is now safely removed.
If {knitr} is absent, an error message is displayed if eng_impl() is somehow invoked. I replaced "knitr" with "{.pkg knitr}", which uses inline markdown to highlight this is a package.
This PR addresses small issues in string formatting.
C:\path\to\temp\dir). However, by convention we use forward slashes everywhere, so I changed it to be consistent with all other displayed paths. Forward slash notation allows to copy-paste paths as is, backslashes are treated as escapes sequences and often require additional escaping.rust_eval_deparse()was previously declared to please R CMD check, but is no longer used. I missed this yesterday when pushed PR. It is now safely removed.{knitr}is absent, an error message is displayed ifeng_impl()is somehow invoked. I replaced"knitr"with"{.pkg knitr}", which uses inline markdown to highlight this is a package.