Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lifting to Path #224

Open
locallycompact opened this issue Sep 5, 2020 · 1 comment
Open

Lifting to Path #224

locallycompact opened this issue Sep 5, 2020 · 1 comment

Comments

@locallycompact
Copy link
Collaborator

Hi, I was initially thinking of wrapping the entire prelude and lifting everything that uses FilePath to use Path, but then I realised there isn't actually a huge amount of things that use FilePath, they're just dotted around in lots of places. Is Path definitely out of scope for RIO and if so is there a way we could organise so as to have a sort of drop-in replacement for FilePath related things?

@snoyberg
Copy link
Collaborator

snoyberg commented Sep 7, 2020

I don't think moving to Path meets the goals of the project. A separate rio-path package makes more sense to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants