Henry Schreiner

@odidev This seems promising, but I'm getting `undefined symbol: _ZTVNSt7__cxx1119basic_ostringstreamIcSt11char_traitsIcESaIcEEE`. Any idea what I might be doing wrong? Also seeing `/usr/bin/find: ‘/host/tmp/install_deps’: No such file or directory` in the repair...

Ahh, I see https://github.com/joerick/cibuildwheel/files/5989984/cffi.patch.txt. Let me look into that. Edit: No, didn't fix it.

To me, it looks like this is being built with a newer GCC than manylinux2014's default (GCC 4.8), but isn't applying the partial static linking trick that RHEL's custom Developer...

hists currently do not change storages under operations. @HDembinski should they? I could probably do that if they should.

I *think* @douglasdavis simply wants this (could be wrong): ```python h = bh.histogram(bh.axis.regular(10,0,1), storage=bh.storage.weight) h.fill([1,2,3], weight=[1,1,1]) h.fill([1,2,3], weight=[2,2,2]) h.fill([1,2,3], weight=[3,3,3]) ``` To be expressible as: ```python h = bh.histogram(bh.axis.regular(10,0,1), storage=bh.storage.weight)...

By the way, I looked at speed a bit, and I think there's a bit to be gained! I had 128 1M element arrays I needed 2D histograms from, and...

I also think it would be helpful to add the numpy to physt example to the docs, since there's a speed benefit.

Extra example: With numba, you can also release the GIL, though for some reason it only works on my macbook or a normal Xeon: ```python from concurrent.futures import ThreadPoolExecutor from...

Here's my post on histogram performance: (all examples eventually produce a Physt histogram)

This would also be (very) useful for boolean, and integer, too, though it can be imitated fairly easily currently. I would expect it to work on all axes, for consistency,...