Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
Assuming there's no way to make you happy with that proposal, what about the proposal for pattern matching? While I understand the desire not to pollute the language with a bunch of eye candy, I also don't think IIFEs are particularly welcome in a project that favors readability, and any other tool I can think of for solving this problem ultimately leads to some kind of mutability that makes code harder to reason about.
Can we please cut the bullshit. By that logic no language is compiled. Because behold, a C interpreter: https://github.com/jpoirier/picoc
I'm just here still waiting for Observables.
eslint-plugin-unicorn’s no-array-for-each rule
eslint-plugin-github’s array-foreach rule (prohibiting forEach)
Here's an example I've quickly written to prove it's true, but you'd need to look at the source code of fp-ts for the implementation.
Related posts
- Six Factors That Raise The Risk Of Bugs In A Codebase
- Deep Cloning Objects in JavaScript, the Modern Way
- Level Up Your TypeScript Projects: Discover the Power of ESLint and Prettier
- How to Do a TypeScript Conversion: an opinionated take on gradual conversions
- Simplify Your Codebase with Auto-Sorting Linter using eslint-plugin-simple-import-sort