SystemFw

object Test {
  case class User(name: String, age: Int)
  case class UserDTO(name: Option[String], age: Option[Int])

  import conversions._

  def a = User("John", 24).convertTo[UserDTO](Set("name"))
  // res0: Test.UserDTO = UserDTO(Some(John),None)

  case class WrongFieldNames(surname: Option[String], age: Option[Int])

danbills

import $ivy.`io.circe::circe-core:0.6.1`
import $ivy.`io.circe::circe-generic:0.6.1`
import $ivy.`io.circe::circe-parser:0.6.1`

import io.circe._
import io.circe.syntax._
import io.circe.parser._
import io.circe.generic.auto._

Tomasvrba

How to capture, stitch and publish a 360° timelapse

Consumer ready 360° cameras are becoming ever more accessible and many people are experimenting with a variety of 360° content. Out of the many cameras on the market the Ricoh Theta S is one of the most user-friendly, turn-key solutions with lots of built-in features. However, the camera's videos are limited 1920x960 resolution and the Theta+ app only lets you create a timelapse with up to 300 or 400 images. The workaround is to use interval shooting to capture as many images as you'd like at the 5376x2688 to full resolution and then stitch them together manually into an HD video. There are few GUI solutions (especially open-source/free) which let you do this with ease. Here's how you do it:

Set up interval shooting on your Ricoh Theta S

joyrexus

collapsible markdown?

CLICK ME

yes, even hidden code blocks!

print("hello world!")

kunanit

import pandas as pd
from sqlalchemy import create_engine

# follows django database settings format, replace with your own settings
DATABASES = {
    'production':{
        'NAME': 'dbname',
        'USER': 'user',
        'PASSWORD': 'pass',
        'HOST': 'rdsname.clqksfdibzsj.us-east-1.rds.amazonaws.com',

noah

#!/bin/sh

KEYDIR=~/.ssh/keys.d/github-deploy
CONFDIR=~/.ssh/config.d/github-deploy

github_username=noah
github_access_token=$(cat ~/.secret/github_access_token)

rp=$(git rev-parse --is-inside-work-tree 2>/dev/null)

smarter

Generalized Algebraic Data Types in Scala

Basic GADTs

Here's an ADT which is not a GADT, in Haskell:

data Expr = IntExpr Int | BoolExpr Bool

ochrons

package poc

import org.scalajs.dom

import scala.scalajs.js
import scala.scalajs.js.annotation.JSExport

@js.native
object WorkerGlobal extends js.GlobalScope {
  def addEventListener(`type`: String, f: js.Function): Unit = js.native

djspiewak

Explaining Miles's Magic

Miles Sabin recently opened a pull request fixing the infamous SI-2712. First off, this is remarkable and, if merged, will make everyone's life enormously easier. This is a bug that a lot of people hit often without even realizing it, and they just assume that either they did something wrong or the compiler is broken in some weird way. It is especially common for users of scalaz or cats.

But that's not what I wanted to write about. What I want to write about is the exact semantics of Miles's fix, because it does impose some very specific assumptions about the way that type constructors work, and understanding those assumptions is the key to getting the most of it his fix.

For starters, here is the sort of thing that SI-2712 affects:

def foo[F[_], A](fa: F[A]): String = fa.toString

rveitch

sass/
|
|– base/
|   |– _reset.scss       # Reset/normalize
|   |– _typography.scss  # Typography rules
|   ...                  # Etc…
|
|– components/
|   |– _buttons.scss     # Buttons
|   |– _carousel.scss    # Carousel