ctreffs

Usage

1. swiftc main.swift -emit-module-path main.swiftmodule -emit-executable -enable-private-imports -Xfrontend -enable-implicit-dynamic
2. ./main -> prints From original bar()
3. swiftc -emit-library inject.swift -o inject.dylib -I . -Xlinker -undefined -Xlinker suppress -Xlinker -flat_namespace -Xfrontend -disable-access-control
4. DYLD_INSERT_LIBRARIES=inject.dylib ./main -> prints From replacement bar()

Notes

• Passing -Xfrontend -enable-implicit-dynamic removes you from having to add dynamic to everything you want to be replacable

ctreffs

// First, let's test out the basic design. This is basically just an 
// HList.

// This recurses to the right because that makes subscripting simpler, 
// at the cost of making appending impossible to generalize.
public protocol TupleProtocol: RandomAccessCollection
    where Index == Int, IndexDistance == Int, Element == Any
{
    associatedtype First
    associatedtype Rest //: TupleProtocol

ctreffs

My hopes for deployable artifacts:

1. Packages would be able to just describe how the things they build should get laid out in a tarball.
2. We would implement this as part of the build, it should be super fast (we might want to consider actually generating the tar directly for portability & control purposes).
3. Packages could have control over the permissions inside the tar file (ideally without having to manipulate the permissions in the filesystem, problematic sometimes if root permission in the tar is desired).
4. The mechanism would support knowing how to handle RPATH issues.
5. The mechanism would know how to handle libswift* portability issues.
6. The mechanism would know how to handle cross-Linux distro issues.
7. Unlike below, I wouldn't expect the mechanism to handle the GIT REVISION stuff, that belongs in a separate proposal.
8. The mechanism would support typical Unix-y things, like bin, lib, libexec, share.
9. The mechanism could support vendored assets like other DSOs or frameworks that can't l

ctreffs

#include <iostream>
#include <vector>

#define GLFW_INCLUDE_VULKAN
#define VK_USE_PLATFORM_WIN32_KHR
#include <GLFW/glfw3.h>

#define GLFW_EXPOSE_NATIVE_WIN32
#include <GLFW/glfw3native.h>

ctreffs

Generic 1,2,3 Noise

float rand(float n){return fract(sin(n) * 43758.5453123);}

float noise(float p){
	float fl = floor(p);
  float fc = fract(p);
	return mix(rand(fl), rand(fl + 1.0), fc);
}

ctreffs

////////////////////////////////////////////////
// CommonProfile Shader v2

#import <metal_stdlib>

using namespace metal;

#ifndef __SCNMetalDefines__
#define __SCNMetalDefines__

ctreffs

struct RelativePointer<Pointee> {
    var offset: Int32

    mutating func advanced() -> UnsafeMutablePointer<Pointee> {
        return withUnsafePointer(to: &self) { [offset] pointer in
            let rawPointer = UnsafeRawPointer(pointer)
            let advanced = rawPointer.advanced(by: Int(offset))
            let pointer = advanced.assumingMemoryBound(to: Pointee.self)
            return UnsafeMutablePointer(mutating: pointer)
        }

ctreffs

// This is a re-implementation of the @Binding and @State property wrappers from SwiftUI
// The only purpose of this code is to implement those wrappers myself just to understand how they work internally and why they are needed
// Re-implementing them myself has helped me understand the whole thing better

//: # A Binding is just something that encapsulates getter+setter to a property

@propertyDelegate
struct XBinding<Value> {
    var value: Value {
        get { return getValue() }

ctreffs

Build settings reference

Active Build Action (ACTION)

A string identifying the build system action being performed.

Additional SDKs (ADDITIONAL_SDKS)

The locations of any sparse SDKs that should be layered on top of the one specified by Base SDK (SDKROOT). If more than one SDK is listed, the first one has highest precedence. Every SDK specified in this setting should be a "sparse" SDK, for example, not an SDK for an entire macOS release.

Alternate Install Group (ALTERNATE_GROUP)

ctreffs

/*
For this Gist, we have two sides: sender and receiver. The same user can be a sender and a receiver, but I will separate this
two roles to be more clear.

This gist assumes thatyou already have a MCSession created, and the peers are connected,
*/