Without this (I think) it is not possible to add new methods for other backends.
Explanation:
In mlr3torch we have some tasks that download data from the internet and they are wrapped in a DataBackendLazy.
In order to still convert the mlr_tasks dictionary to a data.table (without downloading the data) the column information is provided hard-coded and hence requires a custom col_info method.
Without this (I think) it is not possible to add new methods for other backends.
Explanation:
In
mlr3torchwe have some tasks that download data from the internet and they are wrapped in aDataBackendLazy. In order to still convert themlr_tasksdictionary to adata.table(without downloading the data) the column information is provided hard-coded and hence requires a customcol_infomethod.