-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use of std::cbegin causes problems with custom storage classes. #63
Comments
The following is the error. The last version that worked with BAGEL was the one right after Telluride.
|
842b0a5 was the one that worked fine. |
Even if I change that to storage.cbegin(), it does not compile (too many errors to assess...). |
@shiozaki this is leftover from trying to use T* as Storage ... did not work well (required reimplementation of reference_wrapper<T*> or metaprogramming). In 02675d8 implemented std::cbegin/cend/other missing pieces if C++14 is not available. Your classes now should be usable. Please add a separate issue for the compilation errors. |
Thanks. Also the recent changes seem to have fixed the compilation problem. |
Recent changes by Ed breaks BAGEL. In short, that is because my custom storage class has a member function cbegin, but there is no std::cbegin(my_storage).
Yes I know there are cbegin(strorage) and storage.cbegin(), and the former is more fashionable these days in the light of C++11, but I believe introducing a new requirement for mere philosophy is a bad idea.
My suggestion is to use storage.begin() and to wait till std::cbegin is part of the standard.
The text was updated successfully, but these errors were encountered: