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
{{ message }}
This repository has been archived by the owner on Nov 8, 2022. It is now read-only.
In the compiler, this will cause createFlatArray to emit a complaint:
"flattenArray:" "shape mismatch: level 1 expected 2 found 1"
but it won't actually fail; it will go ahead and create pa. Such a ParallelArray is pretty useless. We should probably just prevent them from being created in the first place. (The tutorial already claims that they are "not allowed" -- we should make it so.)
Related: if we get rid of the ability to construct irregular ParallelArrays, then there will be no way (that I know of) to construct a ParallelArray that has false as its flat attribute. All regular ParallelArrays are backed by a single TypedArray and therefore flat: true. So if we disallow irregular ParallelArrays then we can also get rid of any code that deals with flat: false arrays (such as in toString, for example).
The text was updated successfully, but these errors were encountered:
Right now, it is possible to do things like:
In the compiler, this will cause
createFlatArray
to emit a complaint:but it won't actually fail; it will go ahead and create
pa
. Such a ParallelArray is pretty useless. We should probably just prevent them from being created in the first place. (The tutorial already claims that they are "not allowed" -- we should make it so.)Related: if we get rid of the ability to construct irregular ParallelArrays, then there will be no way (that I know of) to construct a ParallelArray that has
false
as itsflat
attribute. All regular ParallelArrays are backed by a single TypedArray and thereforeflat: true
. So if we disallow irregular ParallelArrays then we can also get rid of any code that deals withflat: false
arrays (such as intoString
, for example).The text was updated successfully, but these errors were encountered: