You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a general policy for tuples vs lists in python-land? For example, in Data.Functor in the prelude, I see that tuple is used, but in Data.Array I see that list is used.
If tuples and lists can be used interchangeably, then I'd make sure that the concat operator is changed to something like the code above.
The text was updated successfully, but these errors were encountered:
I think the problem is not from concatArray, the bug should be an array is transformed into a python list, but it should be a tuple.
Is there a general policy for tuples vs lists in python-land? For example, in Data.Functor in the prelude, I see that tuple is used, but in Data.Array I see that list is used.
I would recommend keeping a conversion to tuple and issuing a warning if something is not a tuple. As people add more packages to the FFI, it may be difficult to enforce the use of tuples, and having it crash here makes the system more fragile.
Hi!
I've noticed that sometimes, the function
concatArray
inSemigroup.py
receives alist
and atuple
to concat, which results in the following error:In my local copy of the library, I've changed it to this just to get things working:
But that feels a bit off.
Is there a general policy for tuples vs lists in python-land? For example, in
Data.Functor
in the prelude, I see that tuple is used, but inData.Array
I see thatlist
is used.If tuples and lists can be used interchangeably, then I'd make sure that the concat operator is changed to something like the code above.
The text was updated successfully, but these errors were encountered: