BufferizedNDArray inherits from EagerTensor#394
Conversation
a79ddad to
6aef851
Compare
willow-ahrens
left a comment
There was a problem hiding this comment.
Can bufferizedndarray get moved to be imported after interface? I think it should be imported around the same time we import FIberTensor
|
I was going to ask. I didn't know where to move it so I resorted to update in place. |
|
Why is count nonzeroes in this pr? |
|
|
|
does it? It looks like it's just asking for np.count_nonzeros. The count_nonfill op is implemented in FinchNotation. I think all that's needed there is to convert |
I think the problem here is I need to fix |
|
We're trying to avoid dynamic imports in the library, but I'm not sure what to do about this one. |
|
I tried of bunch of stuff but I think this was the cleanest fix. We can always force the linter to not sort init and we can avoid a bunch of the dynamic imports. |
|
@kylebd99 @mtsokol do you see a way to avoid this dynamic import? The summary is that DCStats uses bufferizedNDArray to accumulate results in finchnotation, but DCStats is defined in autoscheduling module, after the definition of interface. I see two easy fixes:
|
|
Is option 2 above a possibility? |
|
I agree with option 2. It would also fix the other dynamic import that I had to make: autoschedule/compiler.py — from ..compile.lower import make_extent inside _lower_query_of_reorder and _lower_query_of_aggregate. |
#351