connorjclark

const browserCompat = require('@mdn/browser-compat-data');

const browsersToConsider = [
  'chrome',
  'edge',
  'firefox',
  'safari_ios',
  'safari',
];

bterlson

Pattern Matching

This is a strawman proposal for adding pattern matching to ECMAScript. Pattern matching is useful for matching a value to some structure in a similar way to destructuring. The primary difference between destructuring and pattern matching are the use cases involved - destructuring is useful for binding pieces out of larger structures whereas pattern matching is useful for mapping a value's structure to data or a set of behaviors. In practice this means that destructuring tends to allow many shapes of data and will do its best to bind something out of it, whereas pattern matching will tend to be more conservative.

Additionally, the power of pattern matching is increased substantially when values are allowed to participate in the pattern matching semantics as a matcher as well as a matchee. This proposal includes the notion of a pattern matching protocol - a symbol method that can be implemented by objects that enables developers to use those values in pattern matching. A common scenario w

maxim

#!/usr/bin/env ruby

require 'rubygems'
require 'open-uri'
require 'nokogiri'
require 'time'

# USAGE:
# Put ids of IMDB shows here:
movie_ids = %w(tt0773262 tt0121955 tt0182576 tt0460649 tt0903747 tt0412142)

kangax

IE9PP4 bug reports:

• Crash on ES5 strict mode test page
• clientX/clientY (and pageX/pageY) properties are missing on contextmenu events
• Object.freeze(document) kills console
• console.log typeof is "object" instead of "function"
• Some host objects still have "unknown" type
• Object.prototype.hasOwnProperty discrepancy with host objects
• Add HTML5 Element::classList