TIP: Stateful Functions about typescript-book HOT 3 CLOSED

Stateful functions as described are totally unnecessary in JS (and TS by extension). Since it has first-class functions it can easily be achieved with a closure

Thanks 🌹. However you are saying "not needed" followed by "here is how to do them".

Also I do mention using various abstractions that wrap over a local variable. I didn't want to use the term closure to scare newbies 🌹. The pattern I present uses a closure too.

So comparison is between

A.)

const {called} = new class {
    count = 0;
    called = () => {
        this.count++;
        console.log(`Called : ${this.count}`);
    }
};

B.)

const counter = (() => {
  let count = 0;
  return () => {
    count += 1;
    console.log(`Called : ${count }`);
  };
})();

I prefer A 🌹 Also one could use namespace.

from typescript-book.

Yes, sorry, I didn't word that very well. They were two separate statements.

What I meant was the introduction of a "static" keyword would be unnecessary, as there's already a built-in feature capable of achieving the same thing and more.

I can understand that classes are easy to grasp for people coming from a OOP background. However, at run time they are actually functions, and they're an important concept to understand when working in a functional language.

As a suggestion, maybe mention them in passing if you want to avoid confusing the reader with a full example?

edit: spelling

from typescript-book.

and they're an important concept to understand when working in a functional language.

Agreed 🌹 I probably need to add a complete section on JS Fundamentals. But didn't want to add that to this book in particular.

from typescript-book.