- Proposal: SE-NNNN
- Authors: Becca Royal-Gordon
- Review Manager: TBD
- Status: Awaiting implementation (but only of resilience support)
- Implementation: In main and release/6.0, behind the
ObjCImplementation
experimental feature flag - Upcoming Feature Flag:
ObjCImplementation
// Zipping.swift | |
// known-good: Swift 4.2 | |
// Alexis Gallagher | |
import Foundation | |
public extension URL { | |
/// Creates a zip archive of the file or folder represented by this URL and returns a references to the zipped file | |
/// |
This script may no longer work. Have a look at its (more official) replacement: https://github.com/firebase/firebase-tools/tree/master/scripts/examples/hosting/update-single-file
This utility script deploy a single local file to an existing Firebase Hosting site. Other files that are already deployed are left unmodified.
The difference with firebase deploy
is that this script does not require you to have a local snapshot of all hosted files,
you just need the one file that you want to add/update.
- Proposal: SE-NNNN
- Authors: Marc Rasi, Chris Lattner
- Review Manager: TBD
- Status: Awaiting implementation
Swift-evolution thread: https://forums.swift.org/t/pitch-compile-time-constant-expressions-for-swift/12879
{ | |
"audio.dispose": { | |
"body": "audio.dispose( ${1:audioHandle} )", | |
"description": "Releases audio memory associated with the handle.", | |
"prefix": "audio.dispose" | |
}, | |
"audio.fade": { | |
"body": "audio.fade( ${1:[ { [channel=c] [, time=t] [, volume=v ] } ]} )", | |
"description": "This fades a playing sound in a specified amount to a specified volume. The audio will continue playing after the fade completes.", | |
"prefix": "audio.fade" |
import Darwin | |
enum Signal: Int32 { | |
case HUP = 1 | |
case INT = 2 | |
case QUIT = 3 | |
case ABRT = 6 | |
case KILL = 9 | |
case ALRM = 14 | |
case TERM = 15 |
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on
// Let's declare two structs that with different variables and different boolean values: | |
struct A { | |
let x = true | |
} | |
struct B { | |
let y = false | |
} |
ACTION | |
AD_HOC_CODE_SIGNING_ALLOWED | |
ALTERNATE_GROUP | |
ALTERNATE_MODE | |
ALTERNATE_OWNER | |
ALWAYS_SEARCH_USER_PATHS | |
ALWAYS_USE_SEPARATE_HEADERMAPS | |
APPLE_INTERNAL_DEVELOPER_DIR | |
APPLE_INTERNAL_DIR | |
APPLE_INTERNAL_DOCUMENTATION_DIR |