cb372

import java.time.Instant

object Foo {
    case class Timers(
        timer1: Long,
        timer2: Long = Instant.now().toEpochMilli,
        timer3: Long
    )

    val a = Timers(

cb372

import scala.compiletime.S

sealed trait DTList[N <: Int]:
  inline def size: N = valueOf[N]

  def +:[H](h: H): DTNonEmptyList[N, H, this.type] =
    DTNonEmptyList(h, this)

case object DTNil extends DTList[0]
case class DTNonEmptyList[N <: Int, H, T <: DTList[N]](

cb372

TL;DR

We should use a type parameter with a context bound (e.g. F[_]: Sync) in library code so users can choose their IO monad, but we should use a concrete IO monad in application code.

Abstracting over IO

If you're writing a library that makes use of effects, it makes sense to use the cats-effect type classes so users can choose their IO monad (IO, ZIO, Monix Task, etc).

So instead of

cb372

# stick this in your .bashrc/.zshrc
sbtnew() {
  local projectname=$1
  local sbtversion=${2:-1.2.8}
  local scalaversion=${3:-2.12.8}
  cd ~/code
  mkdir $projectname
  cd $projectname
  mkdir project
  echo "sbt.version=$sbtversion" > project/build.properties

cb372

(This is a translation of the original article in Japanese by moratorium08.)

(UPDATE (22/3/2019): Added some corrections provided by the original author.)

Writing your own OS to run on a handmade CPU is a pretty ambitious project, but I've managed to get it working pretty well so I'm going to write some notes about how I did it.

cb372

AWSTemplateFormatVersion: 2010-09-09
Description: >
  Creates a cross-account role that your AWS account can assume
  in order to accept a VPC peering connection in the other account.
  This is pretty confusing, so to clarify,
  1. Run this CloudFormation in the OTHER account to create the cross-account role.
  2. Your account requests a peering connection with the other account.
  3. Your account assumes the role in order to access the other account
     and accept the peering connection.
Parameters:

cb372

# Terminology
their_username = the GitHub username of the contributor who submitted the PR
their_branch = the name of the branch they used to submit the PR
repo_name = the name of your GitHub repository

# First add their fork as a remote
git remote add $their_username git@github.com:${their_username}/${repo_name}.git

# Then fetch it
git fetch $their_username

cb372

import scala.concurrent.ExecutionContext.Implicits.global
import scala.concurrent.Future

import scalacache._
import scalacache.caffeine._
import scalacache.modes.scalaFuture._

type Error = String
type Token = Int

cb372

First of all, sorry for the radio silence. I forgot this channel existed, and Gitter notifications have always been flaky for me.

Second, it sounds like the reasons behind adding a type parameter to Cache are not very clear, so I'll explain below. Maybe I should add some kind of design/architecture page to the microsite?

Third, thank you for all your work on the PR. Sorry again for not being available to give feedback earlier.

cb372

--langdef=scala
--langmap=scala:.scala
--regex-scala=/^[ \t]*((abstract|final|sealed|implicit|lazy)[ \t]*)*(private[^ ]*|protected)?[ \t]*class[ \t]+([a-zA-Z0-9_]+)/\4/c,classes/
--regex-scala=/^[ \t]*((abstract|final|sealed|implicit|lazy)[ \t]*)*(private[^ ]*|protected)?[ \t]*object[ \t]+([a-zA-Z0-9_]+)/\4/o,objects/
--regex-scala=/^[ \t]*((abstract|final|sealed|implicit|lazy)[ \t]*)*(private[^ ]*|protected)?[ \t]*((abstract|final|sealed|implicit|lazy)[ \t ]*)*case class[ \t ]+([a-zA-Z0-9_]+)/\6/C,case classes/
--regex-scala=/^[ \t]*((abstract|final|sealed|implicit|lazy)[ \t]*)*(private[^ ]*|protected)?[ \t]*case object[ \t]+([a-zA-Z0-9_]+)/\4/O,case objects/
--regex-scala=/^[ \t]*((abstract|final|sealed|implicit|lazy)[ \t]*)*(private[^ ]*|protected)?[ \t]*trait[ \t]+([a-zA-Z0-9_]+)/\4/t,traits/
--regex-scala=/^[ \t]*type[ \t]+([a-zA-Z0-9_]+)/\1/T,types/
--regex-scala=/^[ \t]*((abstract|final|sealed|implicit|lazy|override|private[^ ]*(\[[a-z]*\])*|protected)[ \t]*)*def[ \t]+([a-zA-Z0-9_]+)/\4/m,methods/
--re