https://github.com/dhall-lang/dhall-lang/pull/1076#discussion_r498206835 indicates that there's some confusion about the purpose of the Prelude files without the .dhall extension.
When can we remove these files?
@sjakobi: I think one way we can ease the migration is for dhall lint to fix old Prelude imports to use the .dhall extension. Then after a grace period we can remove the extension-free imports.
That'd be great. I've been trying to go through and update stuff where I see it, but I have so many prelude imports scattered through so many projects, haha.
dhall lint change is up here: https://github.com/dhall-lang/dhall-haskell/pull/2061
I don't know if this is only relevant for dhall-haskell, but wouldn't be great to have a mechanism to let users mark a dhall file as deprecated? That way implementations could show a warning when the user imports those files
That way we could mark these old files without the extension as deprecated and the user would notice it
Most helpful comment
@sjakobi: I think one way we can ease the migration is for
dhall lintto fix old Prelude imports to use the.dhallextension. Then after a grace period we can remove the extension-free imports.