Jay Lee Zeta611

Async/Await for Swift

Proposal: SE-XXXX
Authors: Chris Lattner, Joe Groff

Introduction

Modern Cocoa development involves a lot of asynchronous programming using closures and completion handlers, but these APIs are hard to use. This gets particularly problematic when many asynchronous operations are used, error handling is required, or control flow between asynchronous calls gets complicated. This proposal describes a language extension to make this a lot more natural and less error prone.

This paper introduces a first class Coroutine model to Swift. Functions can opt into to being async, allowing the programmer to compose complex logic involving asynchronous operations, leaving the compiler in charge of producing the necessary closures and state machines to implement that logic.

경사스러운 일입니다. 이제 이 곳에 달리는 댓글을 막을 수 있어 그리 하게 되었습니다. 그래도 이전에 달렸던 댓글들은 아무래도 볼 수 있는 다른 방법이 인터넷 상에 존재하긴 하는 모양입니다.

난해한 혀엉... 언어 v0.4.5

…(U+2026), ⋯(U+22EF), ⋮(U+22EE)는 모두 .(U+002E)가 3번 연속으로 나열된 것과 같은 것으로 봅니다.
"한글 음절 문자"는 가(U+AC00) 이상 힣(U+D7A3) 이하의 유니코드 문자들을 의미합니다.

스택

GPG and git on macOS

Setup

No need for homebrew or anything like that. Works with https://www.git-tower.com and the command line.

Install https://gpgtools.org -- I'd suggest to do a customized install and deselect GPGMail.
Create or import a key -- see below for https://keybase.io
Run gpg --list-secret-keys and look for sec, use the key ID for the next step
Configure git to use GPG -- replace the key with the one from gpg --list-secret-keys

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

Ok, I geeked out, and this is probably more information than you need. But it completely answers the question. Sorry. ☺

Locally, I'm at this commit:

$ git show
commit d6cd1e2bd19e03a81132a23b2025920577f84e37
Author: jnthn <[email protected]>
Date:   Sun Apr 15 16:35:03 2012 +0200

When I added FIRST/NEXT/LAST, it was idiomatic but not quite so fast. This makes it faster. Another little bit of masak++'s program.

Answer by Jim Dennis on Stack Overflow question http://stackoverflow.com/questions/1218390/what-is-your-most-productive-shortcut-with-vim/1220118#1220118

Your problem with Vim is that you don't grok vi.

You mention cutting with yy and complain that you almost never want to cut whole lines. In fact programmers, editing source code, very often want to work on whole lines, ranges of lines and blocks of code. However, yy is only one of many way to yank text into the anonymous copy buffer (or "register" as it's called in vi).

The "Zen" of vi is that you're speaking a language. The initial y is a verb. The statement yy is a simple statement which is, essentially, an abbreviation for 0 y$:

0 go to the beginning of this line. y yank from here (up to where?)

	//
	// SpinlockTestTests.swift
	// SpinlockTestTests
	//
	// Created by Peter Steinberger on 04/10/2016.
	// Copyright © 2016 PSPDFKit GmbH. All rights reserved.
	//

	import XCTest


	type ('ty,'v) t =
	\| Nil : ('v, 'v) t
	\| Cons : 'a * ('ty, 'v) t -> ('a -> 'ty, 'v) t

	let cons x l = Cons (x,l)

	let plus1 l = Cons ((),l)

	let one x = Cons (x,Nil)

	# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
	# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
	# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
	# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

	# Add the following to your shell init to set up gpg-agent automatically for every shell
	if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
	source ~/.gnupg/.gpg-agent-info
	export GPG_AGENT_INFO
	else

	# There was a day where I have too many color schemes in iTerm2 and I want to remove them all.
	# iTerm2 doesn't have "bulk remove" and it was literally painful to delete them one-by-one.

	# iTerm2 save it's preference in ~/Library/Preferences/com.googlecode.iterm2.plist in a binary format
	# What you need to do is basically copy that somewhere, convert to xml and remove color schemes in the xml files.

	$ cd /tmp/
	$ cp ~/Library/Preferences/com.googlecode.iterm2.plist .
	$ plutil -convert xml1 com.googlecode.iterm2.plist
	$ vi com.googlecode.iterm2.plist