-
Notifications
You must be signed in to change notification settings - Fork 1k
Open
Labels
breaking-changeissues whose solution would require breaking existing behaviorissues whose solution would require breaking existing behaviorreshapedcast meltdcast melt
Milestone
Description
I'm aware of the other issues that have been raised on this, but am trying to understand the rationale for removing the ability to melt a data.frame entirely, rather than simply switching away from the reshape dependency.
I have previously (perhaps wrongly) taught students to use data.table::melt on data frames. I understand the motivation to move away from reshape, but rather than breaking old code, would it be possible to coerce dataframes to data.table and use the new routines, obviously issuing a warning to the user as it happens?
Metadata
Metadata
Assignees
Labels
breaking-changeissues whose solution would require breaking existing behaviorissues whose solution would require breaking existing behaviorreshapedcast meltdcast melt