khalidx

The experience of using Node.JS with TypeScript, ts-node, and ESM is horrible.

There are countless guides of how to integrate them, but none of them seem to work.

Here's what worked for me.

Just add the following files and run npm run dev. You'll be good to go!

package.json

0xalpharush

# add this to your hardhat config
#     compilers: [
#      {
#        version: "0.8.13",
#         settings: {
#           viaIR: true,
#           outputSelection: {
#             "*": {
#               "*": ["irOptimized"],
#             },

izakpavel

//
//  Lightnings fun
//
//  BEWARE highly unoptimized!
//
//  Created by Pavel Zak on 30/11/2020.
//

import SwiftUI

AvdLee

extension FileManager {
    /*
        Prints out the locations of the simulator and the shared group folder.
        This is useful for debugging file issues.

        Example usage: FileManager.default.printFileLocations()
     */
    func printFileLocations() {
        let paths = NSSearchPathForDirectoriesInDomains(.documentDirectory, .userDomainMask, true)
        let simulatorFolder = paths.last!

Noobish1

import Foundation

protocol MigratableObjectProtocol: Codable {
    associatedtype PreviousObject: Codable
    
    init(previousObject: PreviousObject)
}

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

zwaldowski

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<!-- iOS 10, macOS Sierra, and friends bring a new logging subsystem that's
supposed to scale from the kernel, up to frameworks, and up to apps. It defaults
to a more regimented, privacy-focused approach that large apps and complex
systems need.

It, along with Activity Tracing introduced in iOS 8 and macOS Yosemite and the
Console app in macOS Sierra, hope to help you graduate from caveman debugging to

jkleint

#!/usr/bin/env python
"""
Example of using Keras to implement a 1D convolutional neural network (CNN) for timeseries prediction.
"""

from __future__ import print_function, division

import numpy as np
from keras.layers import Convolution1D, Dense, MaxPooling1D, Flatten
from keras.models import Sequential

plumhead

extension String {
    func size(withAttributes attrs: [String:AnyObject], constrainedTo box: NSSize) -> NSRect {
        let storage = NSTextStorage(string: self)
        let container = NSTextContainer(containerSize: NSSize(width: box.width, height: box.height))
        let layout = NSLayoutManager()
        layout.addTextContainer(container)
        storage.addLayoutManager(layout)
        storage.addAttributes(attrs, range: NSMakeRange(0, storage.length))
        container.lineFragmentPadding = 0.0
        let _ = layout.glyphRangeForTextContainer(container)

mikeash

import Cocoa

enum CoroutineState {
    case Fresh, Running, Blocked, Canceled, Done
}

struct CoroutineCancellation: ErrorType {}

class CoroutineImpl<InputType, YieldType> {
    let body: (yield: YieldType throws -> InputType) throws -> Void