Todd A. Anderson

Prefix is unimportant but it makes the code easier to read than a bunch of meaningless temporary variable names.

My suggestion in the meeting was to add a function, manage_memory_external, that takes does the same thing as manage_memory but takes an extra NRT_ExternalAllocator parameter and then puts that into...

> https://github.com/numba/numba/blob/master/numba/core/runtime/nrt_external.h#L46 > > * `manage_memory` won't work for me as I need to pass additional data to dtor > * `allocate_external` should probably work, I need to check it...

> Can something like `get_stmt_writes` be used instead? Use/def and liveness are used in many places and messing with them is potentially very dangerous. Setitem doesn't really have def semantics....

> Might I propose Arkouda? > > https://github.com/Bears-R-Us/arkouda https://chapel-lang.org/presentations/Arkouda_SIAM_PP-22.pdf Have they improved recently to support more than 1D arrays?

@master-q Please get the latest version of flrc-lib and try the build again.

@master-q Please try again. I guess what happened is that a long time ago there was an API change for some functions to return a pointer instead of a Boolean....

I think I remember a lot of mlton memory problems, even on Linux. As I recall, there was some environment variables or compile option to specify a larger size.

I think I have enabled travis now. I triggered a build on flrc-lib and flrc and they both passed.

@ninegua @rrnewton I'm out of the loop. Why can't Ryan's change just be submitted as a pull request that I can accept?