Simon P. Couch

A bit more context from poking at this for a moment... `tune_args()` methods are intended to return arguments marked for tuning, `tunable()` methods are intended to return arguments marked for...

Agreed, though they do differ in whether there's a default argument and what that default is🤔

We should be able to make much more headway on the listed issues once we don't have to maintain for some foreach edge cases. While we can start in on...

This blog post makes some points that might support adding this feature: https://www.mm218.dev/posts/2024-07-19-tidymodels/

Related to #866—this will be much more attainable once we don't have to maintain some foreach oddities.

Reiterated in a SO post here: https://stackoverflow.com/questions/74815668/is-there-a-metric-for-run-times-or-some-other-recommended-way-to-collect-runtim

Ah, related to https://github.com/tidymodels/tune/pull/880, https://github.com/tidymodels/workflows/pull/191, and friends. :)

Thank you for the issue! Just wanted to let you know this hasn't fallen off our radar. Related to https://github.com/tidymodels/tune/issues/28 and https://github.com/tidymodels/tune/issues/45.

Next step for post-v1.2.0: revert [e79aac1](https://github.com/tidymodels/tune/pull/867/commits/e79aac126dbe6855f4508f4e9941f5748d5c815b) to introduce a deprecation warning when using foreach.

Your `extract` approach you use currently will work fine! The change that will happen once we convert to future is that an interactive logger (that summarizes warnings/errors rather than printing...