Kandelvijaya

I failed to publish OrgNoteApp. I created many small modules in the development process. I call them items in my engineering toolbox. Recently, one of the modules (diffing) is shipped to millions of customers. It’s part success and part learning. Enter FastDiff and its little story.

When do you really want to compare errors? → In the unit tests.

Imagine this scenario. By now you should be aware of how important Result<T> is. If not, you can review the concept with the post Result type in-depth blog.

Functional programming is out there. Partly rumor, partly practiced, partly understood. I have been writing about them for around 6 months. In this post, I want to summarize the main terminologies (jargons) very concisely, with example and best of all, with swift code. For a full explanation, I will link to my previous blogs and external resources as we go along. Lets get going.

Table of Contents Introduction Creating custom operator Operator overload (The bad) Operator overload (The good) Custom Operator Normal composition Direct composition Left to Right application operator Creating Custom Operator |> 3 Q’s before introducing custom operator Custom operator for map fmap or map |» operator Conclusion Introduction Operator (+, -, >) are just normal functions. Treated a bit differently (syntatically) by the compiler.

Table of Contents Keywords Expression Problem Introduction Following the ritual Not following the ritual Preface 2 classical ways to implement analytics library Enum based (Sum type based) Class, struct+protocol based (product type based) Client problem: Add ForceTapEvent & support another analytics service The limitation of enum approach The limitation of class/(struct+protocol) based approach Summarizing A radical way to solve the same issue aka Tagless final Lets get both: ability to add cases and new interpretation.

Table of Contents Writing Testable Swift API with Enums Modeling interface based on Enum Using the OneTapFeature Testing Feature Refactoring the OneTapFearure to make it testable How about testing the present() What if our client module is using Obj-C Is the feature modular? Can it be resused by other apps? Conclusion Writing Testable Swift API with Enums Encapsulate everything and try to show as little as possible. Greedy approach.