Introduce differentiated constructors #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since stateless and stateful React components require different strategies when composing them, it seems reasonable to have different data constructors for the two types.
The proposal is to have
Each constructor would have different implementations for
contramap
and any other function that requires discriminating between the two.Additions
toStateless
: that will be a no-op forStateless
, but will wrap theStateful
with a function and return aStateless
instancecata
and synonymeither
: case analysis, based on the Fantasy Land type proposals Add types fantasyland/fantasy-land#281 and Add polymorphic type catamorphisms fantasyland/fantasy-land#280 respectivelymatch
for case analysis with tags (.match({ Stateless: x => x, Stateful: x => x })
)isStateless : ReactDream -> Boolean
ReactDream
entrypoint will detect the component type and use the corresponding data constructor.To do
ReactDream
functiontoStateless
cata
+either
match