On Mon, Aug 3, 2015 at 8:34 AM, Allen Wirfs-Brock al...@wirfs-brock.com wrote:
[snip]
4) JSON.parse/stringify are pure computational operations. There is no
perf benefit to making them asynchronous unless some of their computation
can be performed concurrently.
If we're speaking strictly
On Mon, Aug 3, 2015 at 10:29 AM, Allen Wirfs-Brock
al...@wirfs-brock.com wrote:
[snip]
I have to guess at your semantics, but what you are trying to express above
seems like something that can already be accomplished using the `reviver`
argument to JSON.parse.
Yes and no. `reviver`
On Tue, Aug 11, 2015 at 2:21 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
[snip]
let Y = F = (x=F(y=(x(x))(y)))(x=F(y=(x(x))(y)));
Aahh! my eyes! it burns!!!
___
es-discuss mailing list
es-discuss@mozilla.org
Dmitrii,
Quick aside: the rude manner in which you are communicating is interfering
with your goal of convincing anyone. Perhaps if you tried not being so
rude, people here would be more willing to listen to what you're saying.
- James
On Fri, Aug 4, 2017 at 1:09 AM Dmitrii Dimandt
Some background as I am the one who added the showProxy feature into
Node.js...
util.inspect() is considered by Node.js to be a diagnostics API. The intent
is to allow adequate debugging in a variety of scenarios. This was added to
address a user issue where inspection of a Proxy object (that the
For many legacy code bases that are based on callbacks mechanisms like
node.js' promisify function are required to help facilitate the transition
from callback centric code to Promise-centric. A lot of the time, these can
follow straightforward rules without requiring customization. However, at
For Node.js we implemented this as an alternative to the current setTimeout:
const { setTimeout } = require('timers/promises')
// Or
import { setTimeout } from 'timers/promises'
Then...
await setTimeout(500)
It works very well and is straightforward to implement on the browser-side.
On Sun,
7 matches
Mail list logo
