-
Notifications
You must be signed in to change notification settings - Fork 58
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
eve::map and callable behavior rework #2013
base: main
Are you sure you want to change the base?
Conversation
36ee952
to
ca0d1d5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused to what's happening. FOr some reason a lot of changes to macros mixed in with some map stuff. Why?
63c6281
to
3dbbbd6
Compare
It is even more files. Github fails to load 650 file diff for me. Please split it up. I believe a lot of changes are independendent. |
a8311aa
to
4019a32
Compare
f309396
to
b143360
Compare
4c6bab5
to
c11ea3d
Compare
c11ea3d
to
cc5ecb1
Compare
EVE_FORCEINLINE constexpr T operator()(T v) const noexcept | ||
{ | ||
return this->behavior(as<T>{}, eve::current_api, this->options(), v); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd argue that a _callable
should deal with passing as<T>
to map.
Asking all of the callers to care about it is a bit extreme.
That means that we might need some new _callable
- but we can deal with that.
If the numbers confirm the perf win, I believe we should do it that way.
@DenisYaroshevskiy let me know what you think