leobalter

// Status of today + dynamic import() proposal, await unwraps namespace objects.

//--- a.js
export let then = async () => {/* code */};

//--- b.js

import * as ns from 'a.js';
async function fn() {
  await Promise.resolve(ns); // should unwrap the "thenable" namespace

leobalter

The "search" event

whatwg/html#667

Some browsers feature non-standard attributes incremental and onsearch for the <input type=search> elements. This also implies the search event being fired.

• Specified? no
• Proposed? no.
  • This link shows a refusal to propose the idea and reasons for it.
• Is it a good idea? no.
• The refusal to proposal the idea bases on the fact it's already redundant with the oninput and onsubmit event handlers

leobalter

var webpack = require('webpack')

module.exports = function (config) {
  config.set({
    browsers: [ 'Chrome' ], //run in Chrome
    browserNoActivityTimeout: 60000,
    singleRun: true, //just run once by default
    frameworks: [ 'mocha' ], //use the mocha test framework
    files: [
      //'src/**/*.{jsx,js}',

leobalter

#!/usr/bin/env perl

use strict;
use warnings;

use Getopt::Long qw(GetOptions);

my $args = '';

GetOptions(

leobalter

Qual o resultado para:

// 1:
{}+{} // ?

// 2:
({}+{}) // ?

leobalter

Site de referência:

https://wiki.mozilla.org/Gaia/Hacking#Building_B2G

Da pasta usuário (~):

hg clone http://hg.mozilla.org/mozilla-central mozilla-central
git clone https://github.com/andreasgal/gaia gaia

leobalter

 yarn test-test262
yarn test-test262 v1.0.2
$ babel-node scripts/test262.js
............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................


harness: Ran 0/181 (0.00%), Passed 0/0 (100%), Failed 0/0 (100%), Skipped 181/181 (100.00%)
intl402: Ran 0/44 (0.00%), Passed 0/0 (10

leobalter

[~/dev/test262-integrator] (master)⚡
 npm test

> test262-integrator@1.0.0 test /Users/leo/dev/test262-integrator
> node test/test.js

......

Failed: test/built-ins/ArrayBuffer/prototype/byteLength/detached-buffer.js
Test262Error: No method available to detach an ArrayBuffer

leobalter

op_list = [
  ("<",  lambda a, b: a < b,  "less-than"),
  ("<=", lambda a, b: a <= b, "less-than-or-equal"),
  (">",  lambda a, b: a > b,  "greater-than"),
  (">=", lambda a, b: a >= b, "greater-than-or-equal"),
]

# This is the hex representation of Number.MAX_VALUE.
max_value_digits = "0xfffffffffffff8" + "0" * 242

leobalter

Original em: http://leobalter.net/cases/escrever-ruby-de-uma-forma-melhor-com-tipagem-ou-codigo-mais-bonito/

Escrever Ruby de uma forma melhor, com tipagem ou código mais bonito!

Depois das ideias super bacanas que a comunidade Ruby trouxe, de fomentar o CoffeScript para escrever um “JavaScript” mais bonito, ou da Google de fazer o Dart para escrever um JavaScript “tipado”, resolvi também trabalhar em algo que deixaria o Ruby perfeito.

Puby e Juby! São dois projetos distintos mas com propósitos excelentes:

Puby