ttscoff

#!/usr/bin/env ruby
# encoding: utf-8
# Marked 2 preprocessor
# Allows use of `*` link references where the next [*]: href defines the link
# Inspired by [tidbits][*]
# [*]: http://tidbits.com
if RUBY_VERSION.to_f > 1.8
	input = STDIN.read.force_encoding('UTF-8')
else
	input = STDIN.read

pabigot

/* See http://blog.regehr.org/archives/1063
 */
#include <type_traits>
#include <cstdint>
#include <limits>
#include <typeinfo>

#ifndef ARGTYPE
#define ARGTYPE uint32_t
#endif /* ARGTYPE */

edwardw

Booting to Rust by Eric Holk! It is just mind-bogglingly cool. What else can I say? His enhancement to Rust has been landed so it is time for me to try that out, in OS X. The setup of the toolchain could be a little bit challenging.

First and foremost, check out the latest Rust with win64 calling convention contributed by Eric Holk and build it.

Then prepare the cross linker.

$ wget http://ftpmirror.gnu.org/binutils/binutils-2.23.2.tar.gz
$ tar xvzf binutils-2.23.2.tar.gz
$ cd binutils-2.23.2
$ mkdir dist

jvns

A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.

I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.

I'd love comments and suggestions about any of these.

I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.

I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".

Kimundi

Update

This Gist now has its own repository on GitHub: https://github.com/Kimundi/lazy-static.rs

mcpherrinm

I want to write Rust code on my computer (x86_64, Ubuntu 14.04) and produce arm executables. I found hints on the internet, but not a concise set of instructions on what to do. So I wrote them down exactly:

apt-get install g++-arm-linux-gnueabihf
git clone https://github.com/mozilla/rust.git
mkdir rust/build-cross
cd rust/build-cross
../configure --target=arm-unknown-linux-gnueabihf --prefix=$HOME/local/rust-cross
make -j8 && make install

bgamari

/*!
 * Intrusive singly linked lists
 */

use std::option::{Option, Some, None};
use std::cell::{Cell};

#[deriving(Show)]
pub struct ListCell<'a, T>(Cell<Option<&'a T>>);

pczarn

Struct layout: total space occupied by padding

(including drop flags and tail padding)

total padding (bytes)	number of structs
0	641
1	6
2	7
3	15

alexcrichton

use std::io;
fn main() {
    println!("digraph \\{");
    let mut input = io::stdin();
    let mut lines = input.lines();
    loop {
        match lines.next() {
            Some(line) => {
                let line = line.unwrap();
                let line = line.as_slice();

kmcallister

states::InHead => match_token!(token {
    CharacterTokens(NotSplit, text) => Split(KeepWhitespace, text),

    CharacterTokens(Whitespace, text) => append_text!(self.target(), text),

    CommentToken(text) => append_comment!(self.target(), text),

    tag @ <base> <basefont> <bgsound> <link> <meta> => {
        self.create_element_nopush(tag.name, tag.attrs);
        Done