Skip to content

Conversation

garyb
Copy link
Member

@garyb garyb commented Apr 17, 2017

This helps communicates the intentions of ArrayView, and prevents any old type being used in there.

People could still create their own invalid foreign data types with the ArrayViewType kind, as we can't close it the way DataKinds would work in Haskell, but it's a little better at least.

@jacereda
Copy link
Contributor

jacereda commented Apr 17, 2017

Yes, much better. And AFAICS, there's no need to bump the major, right?

@garyb
Copy link
Member Author

garyb commented Apr 17, 2017

I don't know really, I think it might be a breaking change - if people are only using the preset ArrayView varieties then it's all good, but if someone is using one of the now-ArrayViewType-kinded types it may be a problem, as if there's no kind annotation at the use site it might not work out anymore. 😕

@jacereda jacereda merged commit 505aa3d into master Apr 17, 2017
@jacereda
Copy link
Contributor

Good, should I publish as v2.0.0?

@jacereda jacereda deleted the kind branch April 17, 2017 21:52
@garyb
Copy link
Member Author

garyb commented Apr 18, 2017

Yeah, I think so. Thanks!

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

Successfully merging this pull request may close these issues.

2 participants