Dave Clayton-Wagner mnem

Swift Concurrency Manifesto

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.

Video game rom codes

You wouldn't download a car...

Primary rom codes

Probably what you're looking for

[a] Alternate (alternate version of the game, usually trying a different output method)
[p] Pirate

API	Status Codes
[Twitter][tw]	200, 304, 400, 401, 403, 404, 406, 410, 420, 422, 429, 500, 502, 503, 504
[Stripe][stripe]	200, 400, 401, 402, 404, 429, 500, 502, 503, 504
[Github][gh]	200, 400, 422, 301, 302, 304, 307, 401, 403
[Pagerduty][pd]	200, 201, 204, 400, 401, 403, 404, 408, 500
[NewRelic Plugins][nr]	200, 400, 403, 404, 405, 413, 500, 502, 503, 503
[Etsy][etsy]	200, 201, 400, 403, 404, 500, 503
[Dropbox][db]	200, 400, 401, 403, 404, 405, 429, 503, 507

PS: If you liked this talk or like this concept, let's chat about iOS development at Stitch Fix! #shamelessplug

Protocol-Oriented Programming in Swift

Speaker: David Abrahams. (Tech lead for Swift standard library)

"Crusty" is an old-school programmer who doesn't trust IDE's, debuggers, programming fads. He's cynical, grumpy.
OOP has been around since the 1970's. It's not actually new.
Classes are Awesome
- Encapsulation
- Access control

#####Gibson Security (aka GibSec, GibsonSec) statement on the latest snapchat blog post.

Follow our twitter (@GibsonSec) or email us at [email protected]

In your blog post, you made a couple statements and you left a few things out, we want (on the behalf of the Snapchat user base) a few things cleared up:

A security group first published a report about potential Find Friends abuse in August 2013. Shortly thereafter, we implemented practices like rate limiting aimed at addressing these concerns. On Christmas Eve, that same group publicly documented our API, making it easier for individuals to abuse our service and violate our Terms of Use.

But is the exploit patched? I wouldn’t want to test, because I might get told “abusing” the service. A phone number, real name (most snapchat usernames i’ve seen have a full name in them) and location (whitepages and the area code) can get you pretty far when yo

Some game dev links.

Quite a few more related to maths here because I suck at maths and need as much help as I can get.

Essential Math for Games Programmers - http://www.essentialmath.com/tutorial.htm
Learning Modern 3D Graphics Programming - http://arcsynthesis.org/gltut/
2D and 3D graphics programming techniques from scratch - http://www.scratchapixel.com
Cheating to make great graphics - http://simonschreibt.de/game-art-tricks/
Game programming patterns - http://gameprogrammingpatterns.com
GPU Gems books at Nvidia developer site: GPU Gems 1, GPU Gems 2, GPU Gems 3

	/*<?php
	///public class PhpJava { public static void main(String[] args) { System.out.printf("/%s",
	//\u000A\u002F\u002A
	class PhpJava {
	static function main() {
	echo(//\u000A\u002A\u002F
	"Hello World!");
	}}
	//\u000A\u002F\u002A
	PhpJava::main();

	Why do compilers even bother with exploiting undefinedness signed overflow? And what are those
	mysterious cases where it helps?

	A lot of people (myself included) are against transforms that aggressively exploit undefined behavior, but
	I think it's useful to know what compiler writers are accomplishing by this.

	TL;DR: C doesn't work very well if int!=register width, but (for backwards compat) int is 32-bit on all
	major 64-bit targets, and this causes quite hairy problems for code generation and optimization in some
	fairly common cases. The signed overflow UB exploitation is an attempt to work around this.

	- (NSArray )tableView:(UITableView )tableView editActionsForRowAtIndexPath:(NSIndexPath *)indexPath {
	UITableViewRowAction moreAction = [UITableViewRowAction rowActionWithStyle:UITableViewRowActionStyleDefault title:@"More" handler:^(UITableViewRowAction action, NSIndexPath *indexPath){
	// maybe show an action sheet with more options
	[self.tableView setEditing:NO];
	}];
	moreAction.backgroundColor = [UIColor lightGrayColor];

	UITableViewRowAction blurAction = [UITableViewRowAction rowActionWithStyle:UITableViewRowActionStyleDefault title:@"Blur" handler:^(UITableViewRowAction action, NSIndexPath *indexPath){
	[self.tableView setEditing:NO];
	}];