Skip to content

Instantly share code, notes, and snippets.

View yupferris's full-sized avatar

Jake Taylor yupferris

957 followers · 389 following
View GitHub Profile
@yupferris
yupferris / chaserTest.hive
Last active August 29, 2015 14:15
Basically lisp.
chaserTest : device "Chaser Test" (0 0)
(
primaryInterval : interval "Primary Interval (60fps)" (20 20) 60
chaserInterval : interval "Chaser Interval (2fps)" (20 100) 2
plasma : plasma "Plasma" (20 180) 36 4
chaser : chaser "Chaser" (20 260)
fadecandy : fadecandy "Fadecandy" (20 340) "127.0.0.1" 7890
primaryInterval.Output -> plasma.Time
primaryInterval.Output -> chaser.Time
@yupferris
yupferris / main.rs
Last active September 27, 2015 15:10
coreaudio-rs memleak drop test
//! A basic output stream example, using an Output AudioUnit to generate a sine wave.
extern crate coreaudio_rs as coreaudio;
extern crate num;
use coreaudio::audio_unit::{AudioUnit, Type, SubType};
use num::Float;
use std::f64::consts::PI;
@yupferris
yupferris / main.rs
Last active September 27, 2015 15:11
coreaudio-rs memleak drop test 2
//! A basic output stream example, using an Output AudioUnit to generate a sine wave.
extern crate coreaudio_rs as coreaudio;
extern crate num;
use coreaudio::audio_unit::{AudioUnit, Type, SubType};
use num::Float;
use std::f64::consts::PI;
@yupferris
yupferris / droptest.rs
Created September 27, 2015 14:27
Rust transmute/ownership isolated drop case
use std::mem;
struct Val {
value: i32
}
impl Val {
fn new(value: i32) -> Val {
println!("Created {}", value);
Val { value: value }
@yupferris
yupferris / droptest-free.rs
Created September 27, 2015 14:33
Rust transmute/ownership drop test using free
extern crate libc;
use std::mem;
struct Val {
value: i32
}
impl Val {
fn new(value: i32) -> Val {
@yupferris
yupferris / gist:1696f6b094a35da40c1a
Created November 3, 2015 20:09
FunScript "clone & go" full output
This file has been truncated, but you can view the full file.
$ git clone [email protected]:ZachBray/FunScript.git
Cloning into 'FunScript'...
remote: Counting objects: 4780, done.
remote: Total 4780 (delta 0), reused 0 (delta 0), pack-reused 4779
Receiving objects: 100% (4780/4780), 54.45 MiB | 4.53 MiB/s, done.
Resolving deltas: 100% (2620/2620), done.
Checking connectivity... done.
$ cd FunScript/
$ chmod +x build.sh # See fix for this in pull request #194
$ ./build.sh
@yupferris
yupferris / prodbgdump.txt
Created December 22, 2015 08:39
$ ./ProDBG/t2-output/macosx-clang-debug-default/ProDBG.app/Contents/MacOS/prodbg
ProDBG_create a
ProDBG_create b
ProDBG_create c
ProDBG_create d
ProDBG_create e
/Users/yupferris/dev/projects/ProDBG/src/prodbg/core/settings.cpp:252 ERROR JSON Error: data/settings.json:(-1:-1) - unable to open data/settings.json: No such file or directory
ProDBG_create f
ProDBG_create g
ProDBG_create h
@yupferris
yupferris / prodbg-happy-spam
Created December 22, 2015 08:43
$ ./t2-output/macosx-clang-debug-default/ProDBG.app/Contents/MacOS/prodbg
ProDBG_create
[0:00:00.003] <570f:0> Started thread 'fs_monitor' (570f) ID 400
BgfxPluginUI::create 0x0 (1024 768)
[0:00:00.018] <570f:0> Started FS event stream for: t2-output/macosx-clang-debug-default
[0:00:00.018] <570f:0> Monitoring file system: t2-output/macosx-clang-debug-default
cerated dock grid 0x0
Unable to load data/current_layout_2.json
fastOpenKey 0x4f5
toggleBreakpointKey 0x1290
@yupferris
yupferris / stack-overflow
Created January 27, 2016 05:01
stack overflow
$ fuse preview
Build started: FullCompile
Configuring
(2,250.51 ms)
Parsing source code
(376.84 ms)
Compiling syntax tree
(1,423.76 ms)
@yupferris
yupferris / rustendo64-contributions.md
Last active February 1, 2016 10:12
A little braindump about some recent PR's and how they align with the project goals

Hey, so I was thinking about yupferris/rustendo64#15, yupferris/rustendo64#20, and yupferris/rustendo64#21, and I'm starting to get the feeling that these contributions might be becoming a bit too significant if that makes any sense. The main point of this project was to document all of the thought processes and resources that went into everything, and the unfortunate part of accepting certain PR's is that we lose quite a lot of that for significant amounts of code that I can't go over on the stream. So, while I certainly appreciate the contributions (they've been great so far), and I'm super stoked you guys are excited about and interested in the project, part of me is a bit on the fence in terms of accepting these.

I can also understand that I hadn't really set a precedent for what I would/wouldn't accept early enough in the project; to be honest I didn't really anticipate receiving any contributions for quite some time. This whole t