You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here, name of effect is repeated 5 times. this makes look of API verbose and makes users be tired of writing name of effects.
Using interface, adding discrimination tag to spec type, having effect representation in variable, mentioning name of spec when creating effect representation seems to be inevitable. But giving name of effect we want to create as string literal seems to be avoidable and I really hope so. let's find a way.
The text was updated successfully, but these errors were encountered:
Here, I share my failed try. I tried to use symbols to dynamically -- and the way user don't notice -- generate identifier of effect representation but found this kind of work would make handler API verbose.
currently, effect representations are created like following:
Here, name of effect is repeated 5 times. this makes look of API verbose and makes users be tired of writing name of effects.
Using interface, adding discrimination tag to spec type, having effect representation in variable, mentioning name of spec when creating effect representation seems to be inevitable. But giving name of effect we want to create as string literal seems to be avoidable and I really hope so. let's find a way.
The text was updated successfully, but these errors were encountered: