proposal-intl-locale-info
proposal-pattern-matching
proposal-intl-locale-info | proposal-pattern-matching | |
---|---|---|
3 | 67 | |
49 | 5,353 | |
- | 1.0% | |
6.6 | 9.0 | |
4 months ago | 19 days ago | |
HTML | HTML | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
proposal-intl-locale-info
-
Updates from 82nd meeting of TC39
Intl Locale Info API part of ECMA402: A proposal to expose Locale information, such as week data (first day in a week, weekend start day, weekend end day, minimun day in the first week), and text direction hour cycle used in the locale.
-
Updates from 80th TC39 meeting
Intl.DisplayNames: enable developers to get translation of language, region or script display names on the client, part of ECMA-402.
-
Updates from 78th meeting of TC39
Intl Locale Info
proposal-pattern-matching
-
Coming to grips with JS: a Rubyist's deep dive
Note, however, that there is a proposal to add pattern matching to JS.
-
Level up your Typescript game, functionally - Part 2
There's an ECMAScript proposal that is in the works to add this feature to the language! It's going to look something like this.
-
Building React Components Using Unions in TypeScript
More importantly, TypeScript typically commits to build things into itself when the proposal in JavaScript reaches Stage 3. The pattern matching proposal in JavaScript is Stage 1, but depends on many other proposals as well that may or may not need to be at Stage 3 as well for it to work. This particular proposal is interested on pattern matching on JavaScript Objects and other primitives, just like Python does with it’s native primitives. These are also dynamic types which helps in some areas, but makes it harder than others. Additionally, the JavaScript type annotations proposal needs to possibly account for this. So it’s going to be awhile. Like many years.
-
Explicit Software Design. Preliminary Conclusions
For true™ functional programming in JS, native pattern matching and partial function application are missing (at least for now: 1, 2). For proper OOP, it lacks real interfaces and compile-time dependency injection.
-
TypeScript Is Surprisingly OK for Compilers
The proposal for pattern matching syntax seems more akin to what they're looking for.
https://github.com/tc39/proposal-pattern-matching
-
[AskJS] C# in every Node.js job posting?
There's a proposal to add something like that to JavaScript but it's been stuck in limbo since 2017 although there are libraries like ts-pattern which implement it already.
-
[AskTS] What do you think will be the future of runtime type checking?
I'll admit, it is easy to assert that the TypeScript language should not be involved in the matters of packages but I also wonder if we're moving towards a point where interfaces will be as common as namespaces and whether or not it would be sensible for the language to incorporate such type assertions into the language formally, after all, it already compiles to various forms of JavaScript and there is a stage 1 proposal submitted to the TC39 committee to give JavaScript pattern matching. If adopted, wouldn't it make sense to allow TypeScript to compile a type into a type guard for the native JavaScript pattern matcher?
- Updates from the 96th TC39 meeting
-
Mostly adequate guide to FP (in JavaScript)
Both are active tc39 proposals :)
https://github.com/tc39/proposal-pipeline-operator - Stage 2
https://github.com/tc39/proposal-pattern-matching - Stage 1
Hopefully we get both in the next couple of years.
-
CoffeeScript for TypeScript
We often add promising TC39 proposals into Civet so people can experiment without waiting.
We've added https://github.com/tc39/proposal-pipeline-operator, a variant of https://github.com/tc39/proposal-pattern-matching, a variant of https://github.com/tc39/proposal-string-dedent and others.
Since our goal is to be 99% compatible with ES we'll need to accommodate any proposals that become standard and pick up anything TC39 leaves on the table (rest parameters in any position, etc.)
What are some alternatives?
proposal-intl-enumeration - Return supported values of options, such as timeZone, calendars, numberingSystems, currencies, units
fp-ts - Functional programming in TypeScript
proposal-json-modules - Proposal to import JSON files as modules
package.elm-lang.org - website for browsing packages and exploring documentation
proposal-class-static-block - ECMAScript class static initialization blocks
content - The content behind MDN Web Docs
proposal-array-find-from-last - Proposal for Array.prototype.findLast and Array.prototype.findLastIndex.
ecma262 - Status, process, and documents for ECMA-262
proposal-string-dedent - TC39 Proposal to remove common leading indentation from multiline template strings
proposal-pipeline-operator - A proposal for adding a useful pipe operator to JavaScript.
proposal-intl-DateTimeFormat-formatRange - ECMA 402 proposal for DateTimeFormat.prototype.{formatRange,formatRangeToParts}
proposal-record-tuple - ECMAScript proposal for the Record and Tuple value types. | Stage 2: it will change!