<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Functional-Programming on Ahmed Nadeem</title><link>https://ahmed-deftoner.github.io/blog/tags/functional-programming/</link><description>Recent content in Functional-Programming on Ahmed Nadeem</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 09 Apr 2024 22:45:32 +0500</lastBuildDate><atom:link href="https://ahmed-deftoner.github.io/blog/tags/functional-programming/index.xml" rel="self" type="application/rss+xml"/><item><title>Pipes and Composition in TypeScript</title><link>https://ahmed-deftoner.github.io/blog/posts/ts-pipes/</link><pubDate>Tue, 09 Apr 2024 22:45:32 +0500</pubDate><guid>https://ahmed-deftoner.github.io/blog/posts/ts-pipes/</guid><description>TypeScript does not have a built-in pipe operator (unlike some other languages), but the idea is everywhere: take a value, run it through a sequence of small functions, and get a result. When you structure code that way, you are doing Functional Composition: building a larger transformation out of smaller, reusable pieces.
Composition: compose vs pipe Link to heading Composition ties functions together so the output of one feeds the next.</description></item></channel></rss>