Hans Dembinski
Hans Dembinski
Adding @pfackeldey as another person interested in this feature. It should be really implemented on the upper level in C++ Boost Histogram. I will try to work on this ASAP,...
Prototype for experimenting ```c++ #include #include #include #include int main() { namespace bh = boost::histogram; struct axis { using value_type = boost::rational; using index_type = bh::axis::index_type; index_type num_; value_type offset_;...
@alexander-held I use this feature myself. I fit invariant-mass distributions in eta and pt of some particle. Then I store the fitted particle yield and its uncertainty squared as "values"...
No, but long constructors with many keywords are not a good design. It is not significantly more efficient to do this instead of assigning.
> Comment from the 🥜 gallery: if you are going to have many end-users all extending the class to add a sub-set of the keyword arguments you can end up...
I am not super committed to this proposal, I mainly added this here as an anchor for discussion. I am personally fine with not adding too many ways of doing...
The problem with a "smart locator" is that it breaks some fundamental design principles. In well designed interfaces, everything is plain and obvious and consistent. We hate it when stuff...
@jpivarski Henry wants smart locators, I think they are a bad idea. @henryiii seems to believe that you were also in favor of "context-aware" locators, but I think it goes...
It seems that the iterators returned by `indexed` do not satisfy the `std::input_or_output_iterator` concept. https://en.cppreference.com/w/cpp/iterator/input_or_output_iterator It is not immediately obvious why, so this is needs more digging. Technically, they should...