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

Deprecate this package for 0.12? #13

Open
paulyoung opened this issue Jun 13, 2018 · 8 comments
Open

Deprecate this package for 0.12? #13

paulyoung opened this issue Jun 13, 2018 · 8 comments

Comments

@paulyoung
Copy link

I was reviewing paulyoung/purescript-prettier-printer#12 and it looks like this package may be redundant for 0.12 paulyoung/purescript-prettier-printer#12 (comment)

Thanks for providing this up until now, and apologies in advance if I'm mistaken 🙇

@paulyoung
Copy link
Author

I was thinking something along the lines of what purescript-maps and other packages have done might be helpful.

Something like a migration guide in the README would be good.

@i-am-tom
Copy link
Collaborator

Not sure I follow - what has 0.12 introduced? (Genuinely curious as I use this library in a few places)
I think the point could be made that this library is essentially liftEff (and later liftEffect) over a few quickCheck functions - is this a Fairbairn threshold thing?

@paulyoung
Copy link
Author

0.12 made Effect the default for effects, so in paulyoung/purescript-prettier-printer#12, we can just do this:

-import Test.QuickCheck (class Arbitrary, arbitrary, (===))
+import Test.QuickCheck (class Arbitrary, arbitrary, (===), quickCheck)
-import Test.Spec.QuickCheck (QCRunnerEffects, quickCheck)

@paulyoung
Copy link
Author

...and also this:

-spec :: Spec (QCRunnerEffects ()) Unit
+spec :: Spec Unit

@paulyoung
Copy link
Author

Note the use of liftEffect as well.

-it "is a homomorphism from addition to composition" do
+it "is a homomorphism from addition to composition" $ liftEffect do

@i-am-tom
Copy link
Collaborator

Oh, I see - spec-quickcheck was useful for hiding away some ugly liftEff and its effects declaration, but now it's only useful for the former?

@paulyoung
Copy link
Author

I think so, but that's what I'm trying to determine with this issue.

@i-am-tom
Copy link
Collaborator

This makes sense to me - I think ultimately it'll be @owickstrom's decision, but I agree that there's maybe not a lot of utility here anymore. I'll leave this around for when Oskar has time to review it, but I'm definitely inclined to agree!

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