<button>Let's Go !</button>
This vanilla ES6 function async
allows code to yield
(i.e. await
) the asynchronous result of any Promise
within. The usage is almost identical to ES7's async/await
keywords.
async/await
control flow is promising because it allows the programmer to reason linearly about complex asynchronous code. It also has the benefit of unifying traditionally disparate synchronous and asynchronous error handling code into one try/catch block.
This is expository code for the purpose of learning ES6. It is not 100% robust. If you want to use this style of code in the real world you might want to explore a well-tested library like co, task.js or use async/await
with Babel. Also take a look at the official async/await
draft section on desugaring.
- node.js - 4.3.2+ (maybe earlier with
import { NgModule } from '@angular/core'; | |
import { BrowserModule } from '@angular/platform-browser'; | |
import { SafeHtmlPipe } from "./pipes" | |
@NgModule({ | |
declarations: [ | |
SafeHtmlPipe, |
- Create certificate
- Config Apache to access
https
instead ofhttp
- Config mod rewrite to generate SSL url
- Config Virtual host to test site
- Go to your XAMPP installation directory (in my case it’s E:\xampp), figure out apache folder. In this, find & run batch file
'use strict'; | |
import Singleton from 'Singleton'; | |
class ClassA extends Singleton { | |
constructor() { | |
super(); | |
} | |
singletonMethod1() { | |
// ... |
<?php | |
var_dump(file_exists("Contracts/AppDev/AppAuthInfo.php")); | |
require_once('../vendor/autoload.php'); | |
use Mozu\Api\Contracts\AppDev\AppAuthInfo; | |
use Mozu\Api\MozuConfig; | |
use Mozu\Api\ApiContext; |
// Comcast Cable Communications, LLC Proprietary. Copyright 2014. | |
// Intended use is to display browser notifications for critical and time sensitive events. | |
var _ComcastAlert = (function(){ | |
return { | |
SYS_URL: '/e8f6b078-0f35-11de-85c5-efc5ef23aa1f/aupm/notify.do' | |
, dragObj: {zIndex: 999999} | |
, browser: null | |
, comcastCheck: 1 | |
, comcastTimer: null | |
, xmlhttp: null |
Document moved to: https://github.com/servo/servo/blob/master/HACKING_QUICKSTART.md
function mapValues(obj, fn) { | |
return Object.keys(obj).reduce((result, key) => { | |
result[key] = fn(obj[key], key); | |
return result; | |
}, {}); | |
} | |
function pick(obj, fn) { | |
return Object.keys(obj).reduce((result, key) => { | |
if (fn(obj[key])) { |
📂 Persistent "pipes" in Linux
In a project I'm working on I ran into the requirement of having some sort of persistent FIFO buffer or pipe in Linux, i.e. something file-like that could accept writes from a process and persist it to disk until a second process reads (and acknowledges) it. The persistence should be both across process restarts as well as OS restarts.
AFAICT unfortunately in the Linux world such a primitive does not exist (named pipes/FIFOs do not persist