Arnaud Spiwack

That wouldn't be correct anyway, since with this definition `getIdentity . newArray @Identity` would have type `Int -> Array`, and this is wrong (it gives me no way of imposing...

Maybe? That would actually be a helpful item, since all the convenience function would work for every source bearing type like this. Something like ```haskell data Source instance Dupable Source...

That's a fair point. So, in order to fill the blanks, we would need an extra type family attached to the type class. And have `grab` take extra argument of...

@utdemir this is an interesting enough question that we ought to make a separate issue to discuss it. This comment will act as a link between the two issues.

I want to share some further development on this issue. In that, I think that I know the solution _but_ it requires GHC support and will take a little time...

This wouldn't introduce backwards incompatible change. So I'll downgrade it to after-first-milestone status.

The reason for this is simple: linear-base has existed for longer than `-XUnliftedDatatypes`. I haven't thought of what it would take to have better support for unlifted datatypes. What would...

You can't really change the `Monoid` type class: it has the correct definition. And, yes, it does imply that `Ur mempty :: Ur a` is well typed. For all monoids....

> That makes me uneasy. Combined with a `mempty :: Array a`, it feels like now we have a way to get any array as `Unrestricted`. This might be incorrect,...

> I don't understand. Wouldn't `push empty a` be an unrestricted non-empty vector? You are absolutely right. An unrestricted empty vector would be no good. In a way, it's reassuring:...