Simon P. Couch

Just confirming that I'm able to reproduce this. Somewhat reminds me of #117—may need to revisit.

For a stack `st`, the slot `attr(st$coefs$preproc$terms, ".Environment")` is inflated after saving. This can be replicated even without butcher. ``` r library(tidymodels) library(stacks) st % add_candidates(class_res_nn) %>% add_candidates(class_res_rf) %>% blend_predictions()...

Related-ish to #118.

This is likely a matter of passing `required_pkgs(workflow)` to `.options.future`.

This may actually be a model registration issue--see https://github.com/tidymodels/parsnip/issues/1128.

Based on that reprex in parsnip, I'm going to go ahead and close—we shouldn't need to pass any future options there, instead relying on `set_dependency()` calls in the model registration....

With an eye for reducing `Remotes` hoopla, I'm going to go ahead and merge and open issues for smaller todos.

You're correct that there's not an option to show that xgboost output! A reprex: ``` r library(tidymodels) bt_mod % set_engine("xgboost", verbose = 1) bt_mod_tune % set_engine("xgboost", verbose = 1) bt_fit...

Heard. I agree that we ought to look into this! Just wanted to add here that this is also the case with CRAN tune, so this wasn't an unintended side...

Wasn't sure whether to apply `bug` or `feature`, but either way, I agree that this ought to be fair game. :)