Skip to content

Conversation

Quuxplusone
Copy link
Contributor

I'll do map_error and or_else also; just poking the CI.
This depends on (i.e., is a superset of) #99.

…ess.

This incidentally simplifies the preprocessor stuff, by making these
codepaths look the same in both C++11 and C++14. The old code had the
weird effect that the C++11 codepath was slightly *more* SFINAE-friendly
than the C++14 codepath.

This patch doesn't actually make and_then/map/transform/map_error/or_else
be SFINAE-friendly. But it lays the groundwork for adding further
constraints to the `enable_if` stuff in `and_then_impl` etc., which
could make these functions fully SFINAE-friendly without needing to
touch the non-`_impl` versions again.
This mainly just swaps two big blocks of code. But it also
adds `detail::` in front of every call to `foo_impl`; and
it renames `expected_map_impl` to simply `map_impl` because
that seems more consistent with the rest of the names.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant