An update on Object.observe
Over three years ago, Rafael Weinstein, Erik Arvidsson, and I set out to design and implement what we believed to be the primitive underlying the data-binding system of MDV ("model-driven views"). We prototyped an implementation in a branch of V8, then got agreement from the V8 team to build a real version upstream, while pushing Object.observe ("O.o") as a part of the upcoming ES7 standard and wo
Web Platform WG F2F -- 26 Oct 2015
Present paulc, hober, kochi, adrianba, Karl_Dubost, dom, Koji_Ishii, mathieucitrix, MikkoT, Dan_Appelquist, xiaoqian, Gary_Kacmarcik, Jean-Claude_Dufourd_(Institut_Mines_Telecom), hayato, Arnaud_Braud, markw, JT_Jung, Josh_Soref, dcooney, Yves, Wayne_Carr, Sebastian_Kaebisch, koji, LJWatson Regrets Chair chaals Scribe timeless, Dan A. <inserted> scribe: timeless Agenda Bashing for Tuesday chaals:
ECMAScript 6 destructuring gotcha - Human Who Codes
With all of the new syntax in ECMAScript 6, you’re bound to periodically find something that is confusing (likely as you’re hunting down an error). Recently, I’ve seen an uptick in the reporting of a specific type of error as it relates to destructuring assignment[1] using object patterns. Destructuring basics Before you can understand the problem, it’s helpful to look at a few examples of destruc
JavaScript in TypeScript compilations · Issue #4792 · microsoft/TypeScript
JavaScript in TypeScript compilations (See parent issue #4789 for an overview) There are a number of considerations for the TypeScript compiler to handle JavaScript code: Should the compiler automatically pick up JavaScript files in a folder as it does for TypeScript? If so, how to avoid compiling JavaScript files that were emitted by a prior TypeScript compilation? Should the compiler emit JavaSc
Security consideration: Multi-threading helps cache-based side channel attacks · Issue #1 · lars-t-hansen/ecmascript_sharedmem · GitHub
Shared memory allows the construction of a high-resolution timer (nanosecond resolution), which enables cache-based side channel attacks, such as those described in the paper "The Spy in the Sandbox -- Practical Cache Attacks in Javascript" (http://arxiv.org/abs/1502.07373). For example, key press handling code produces a detectable signature of accesses to L3 cache sets. An attacker can use timin
25981 – ES6 integration
https://mail.mozilla.org/pipermail/es-discuss/2014-July/038406.html When an event loop is created, invoke the algorithm in 8.5 Initialization. Step 7 should obtain zero scripts. This results in 8.4.2 NextTask being invoked. 8.4.2 NextTask is adjusted as follows: The "implementation defined unhandled exception processing" in step 1 must be the "report an error" logic in the HTML spec. The "implemen
Why does forEach throw away the return value while map/filter pass it through unchanged? · Issue #27 · tc39/proposal-observable
I realize map/filter are provisional. But in general it's unclear to me how the return value/exception is supposed to integrate with all this. Another related question is why any thrown exception gets passed through as a promise rejection while the return value gets ignored. Can we use iterator map/filter/forEach to inform the design here? I'm not sure how exactly, but it would be nice, because ri
Use cases for synchronous subscription. · Issue #38 · tc39/proposal-observable
It would be great if we had a list of use cases for synchronous subscription in order to better understand if/when [Symbol.observer] is needed. Please include: Description - Why is this use case important and who are the users. Code - a minimal example demonstrating the use case and showcasing it. preferably codepen/jsbin/jsfiddle but a gist is also fine, demonstrating the issue. Why synchronous s
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Does this work with ES6/2015 imports? · Issue #90 · ternjs/tern_for_sublime
Kill CommonJS default export behaviour · Issue #2212 · babel/babel
privates.md
Destructuring declarations that bind nothing should probably be an early error · Issue #97 · tc39/ecma262
https://github.com/rwaldron/tc39-notes/blob/master/es7/2015-09/sept-22.md
1185106 - Implement async functions (ES 2017 proposal)
Chrome 44 (Canary) introduces breaking changes within MooTools · Issue #2711 · mootools/mootools-core
Bug 4432 – String.prototype.split should revert to ES5 behavior, using ToUint32 to coerce limit argument
1135708 - Implement exponentiation operator (ES7 proposal)
Results of TC39 presentation · Issue #37 · tc39/proposal-regex-escaping
1178932 - Implement ES6 Reflect.construct
Putting `global` reference in specs