stephantabor

var Promise = require('bluebird');

var funcs = Promise.resolve([500, 100, 400, 200].map((n) => makeWait(n)));

funcs
  .each(iterator)       // logs: 500, 100, 400, 200
  .then(console.log)    // logs: [ [Function], [Function], [Function], [Function] ]

funcs
  .mapSeries(iterator)  // logs: 500, 100, 400, 200

redrabbit

defmodule Absinthe.Ecto.Resolution.Schema do
  @moduledoc """
  This module provides helper functions to resolve a GraphQL query into `Ecto.Query`.
  """
  import Absinthe.Resolution.Helpers
  import Ecto.Query

  alias Absinthe.Resolution
  alias Absinthe.Blueprint.Document.Field

justinwoo

Reposted from Qiita

For almost a year now, I've been using this "flux" architecture to organize my React applications and to work on other people's projects, and its popularity has grown quite a lot, to the point where it shows up on job listings for React and a lot of people get confused about what it is.

Why I'm tired of using and teaching flux

There are a billion explainations on the internet, so I'll skip explaining the parts. Instead, let's cut to the chase -- the main parts I hate about flux are the Dispatcher and the Store's own updating mechanism.

If you use a setup similar to the examples in facebook/flux, and you use flux.Dispatcher, you probably have this kind of flow:

bsedat

FROM elixir:1.4.5 as asset-builder-mix-getter

ENV HOME=/opt/app

RUN mix do local.hex --force, local.rebar --force
# Cache elixir deps
COPY config/ $HOME/config/
COPY mix.exs mix.lock $HOME/
COPY apps/myproject_web/mix.exs $HOME/apps/myproject_web/
COPY apps/myproject_web/config/ $HOME/apps/myproject_web/config/

johanneswuerbach

---
language: objective-c
before_script:
- ./scripts/travis/add-key.sh
after_script:
- ./scripts/travis/remove-key.sh
after_success:
- ./scripts/travis/testflight.sh
env:
  global:

stevedonovan

use std::rc::Rc;
use std::cell::{RefCell,Ref, RefMut};
use std::ops::Deref;
use std::fmt;

#[derive(Clone)]
struct Shared<T> {
    v: Rc<RefCell<T>>
}

davbeck

#!/usr/bin/env ruby

require "active_support"


def assetCatalogsAtPath(path)
	results = []
	
  contents = Dir.entries(path)
  

bpo

redis-cli EVAL "$(cat hello.lua)" 0

mbrandonw

Copy and paste the swift code below into a playground to experiment.

This is a very close emulation of Functor and Monad typeclasses in swift. However, it is very fragile (i.e. easy to crash the compiler).

For example, instance methods of fmap will run fine, but attempting to use a globally defined fmap that acts on Functor types will cause a crash. Similarly for bind. Unfortunately this means we cannot define the nice infix operator versions of these functions.

harlanhaskins

Copy and paste the swift code below into a playground to experiment.

This is a very close emulation of Functor and Monad typeclasses in swift. As of Swift 1.2 and Xcode 6.3, this is no longer very fragile.

Unfortunately, the compiler cannot verify the types when passing a function to (>>=). We have to wrap the function in a closure and call it with an explicit argument to compile.

optionalDoubles >>= squareRoot // doesn't compile
optionalDoubles >>= { squareRoot($0) } // compiles