Hans Dembinski

BLOSC is BSD licensed, so compatible with BSL. https://www.blosc.org/pages/blosc-in-depth/ https://github.com/Blosc/c-blosc2

It is open what the accumulator does with the initial arguments. For the currently builtin accumulators, this feature makes not much sense. But you could come up with some user-defined...

A PR for a rolling mean would be very appreciated, thanks! The implementation should not use circular_buffer though, to not add another dependency to boost::histogram. Enduser code should make of...

I made this comment before: it is generally bad design to make objects context aware. I wrote down the alternative, which is to replace the slice object instead of making...

I forgot the argument about bh.overflow.

> In our call, the main outcome was that that locators needed to be smarter (this was @jpivarski's idea, and we all agreed on this). That was not the main...

I can include the underflow or overflow bin already by not specifying the lower or upper bound in the slice, which is perfect for me and I think also for...

> Your new value_slice object is completely against the design of UHI. The U in UHI stands for Unified or Universal - anyone can write a locator, and they don't...

Summary: Context-aware locators are bad. For consistency, locators should behave in a slice exactly like they behave in getitem.

Follow-up: this works ``` v.value[v.value == 2] = [3] # ok, v.value is now [1, 3, 3] ``` I guess this kind of behavior makes sense. The second version calls...