Change enum assoc values to Config for consistency, remove <*> op #5

Merged
merged 1 commit into from Oct 21, 2015

Projects

None yet

2 participants

@SixFiveSoftware
Contributor

Config: Just used the type-aliased Config type rather than explicitly stating the
params and their types again, for consistency.
<>: Great operator, but in this case the <^> and <> ops both have the same
signature, and do the exact same thing ultimately, so <*> is not needed.

@SixFiveSoftware SixFiveSoftware Change enum assoc values to Config for consistency, remove unnecessar…
…y <*> operator.

Config: Just used the type-aliased Config type rather than explicitly stating the
params and their types again, for consistency.
<*>: Great operator, but in this case the <^> and <*> ops both have the same
signature, and do the exact same thing ultimately, so <*> is not needed.
4eecf3e
@terhechte terhechte merged commit 23f36e2 into terhechte:master Oct 21, 2015
@terhechte
Owner

Good Idea, thanks for the PR. That nicely simplifies this example.

@SixFiveSoftware
Contributor

👍 Great article! Thanks for sharing.

@SixFiveSoftware SixFiveSoftware deleted the SixFiveSoftware:fix/refactor_functional_Config_example branch Oct 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment