ethanhuang13

//
//  VirtualKeyboard.swift
//  MacBook Air M1 Zhuyin Keyboard
//  Written with SwiftUI ~=300 LOC, < 4hrs
//  Created by Ethan Huang on 2021/1/13.
//  Twitter: @ethanhuang13

import SwiftUI

struct VirtualKeyboard: View {

steipete

/// Higher-order functions for `NSDictionary`.
@interface NSDictionary <KeyType, ObjectType> (PSPDFFoundation)

/// Converts the current dictionary into a case insensitive one.
@property (nonatomic, readonly) NSDictionary<NSString *, ObjectType> *pst_caseInsensitiveDictionary;

@end

ethanhuang13

//
//  FacebookAuth.swift
//  GitHub: ethanhuang13
//  Twitter: @ethanhuang13

import AuthenticationServices
import SafariServices

/*
 Updated: 

mecid

import SwiftUI

extension Calendar {
    func generateDates(
        inside interval: DateInterval,
        matching components: DateComponents
    ) -> [Date] {
        var dates: [Date] = []
        dates.append(interval.start)

pofat

import Foundation
import UIKit

UIApplicationMain(CommandLine.argc, CommandLine.unsafeArgv, NSStringFromClass(UIApplication.self), NSStringFromClass(AppDelegate.self))

// Remeber to comment or remove `@UIApplicationMain` in your AppDelegate.swift

NSExceptional

Edit Feb 4 5:16 PM: Skip to the bottom if you just want the article

It has been brought to my attention that rehosting someone else's content without asking them — even if you link to the original content — is not exactly polite. I did not ask the author before I rehosted his article, and while I feel I should have known better than to that, it just didn't occurr to me. It's not exactly plagarism, but it's still wrong on some level. I have reached out to him now about hosting it here publically, and if he says it's alright, I'll put it back.

You can find the original article here, on his site, and on his Medium page.

almaleh

class ViewController: UIViewController {
    let concurrent = DispatchQueue(label: "com.besher.concurrent", attributes: .concurrent)
    let isolation = DispatchQueue(label: "com.besher.isolation", attributes: .concurrent)
    private var _array = [1,2,3,4,5]
    
    var threadSafeArray: [Int] {
        get {
            return isolation.sync {
                _array
            }

zntfdr

// How to:
//  1. Open the Firebase Analytics Dashboard
//  2. Scroll to bottom, where you see the "Users by Device model" widget
//  3. Click "View device models" in that widget (this opens the "Tech details" Firebase Analytics page)
//  4. Above the table shown in the new page, click on the “Device model” drop down menu and select “OS with Version”
//  5. Make sure to select “OS with version” and not “OS Version”
//  6. On the top right corner of the page, click on the “Share this report” icon (next to the date)
//  7. Click “Download file” on the new side bar, then “Download CSV"
//  8. Open the file and select the iOS/Android breakdown raw data
//  9. Replace the sample data in this script with your data

chriseidhof

//
//  ContentView.swift
//  DeleteMe
//
//  Created by Chris Eidhof on 02.02.21.
//

import SwiftUI

/*

tclementdev

libdispatch efficiency tips

The libdispatch is one of the most misused API due to the way it was presented to us when it was introduced and for many years after that, and due to the confusing documentation and API. This page is a compilation of important things to know if you're going to use this library. Many references are available at the end of this document pointing to comments from Apple's very own libdispatch maintainer (Pierre Habouzit).

My take-aways are:

• You should create very few, long-lived, well-defined queues. These queues should be seen as execution contexts in your program (gui, background work, ...) that benefit from executing in parallel. An important thing to note is that if these queues are all active at once, you will get as many threads running. In most apps, you probably do not need to create more than 3 or 4 queues.

• Go serial first, and as you find performance bottle necks, measure why, and if concurrency helps, apply with care, always validating under system pressure. Reuse