ayosec

#![feature(core)]
extern crate core;
use core::fmt;

struct Color {
    r: u8,
    g: u8,
    b: u8,
}

ayosec

#![feature(core)]
extern crate core;
use core::fmt;

struct Color {
    r: u8,
    g: u8,
    b: u8,
}

ayosec

scala> :paste
// Entering paste mode (ctrl-D to finish)

import play.api.libs.json._
import spray.http._
import MediaTypes._
import spray.client.pipelining.Post
import spray.httpx.marshalling.Marshaller

case class Foo(a: Int, b: String)

ayosec

Rust developer tools - status and strategy

Availability and quality of developer tools are an important factor in the success of a programming language. C/C++ has remained dominant in the systems space in part because of the huge number of tools tailored to these lanaguages. Succesful modern languages have had excellent tool support (Java in particular, Scala, Javascript, etc.). Finally, LLVM has been successful in part because it is much easier to extend than GCC. So far, Rust has done pretty well with developer tools, we have a compiler which produces good quality code in reasonable time, good support for debug symbols which lets us leverage C++/lanaguge agnostic tools such as debuggers, profilers, etc., there are also syntax highlighting, cross-reference, code completion, and documentation tools.

In this document I want to layout what Rust tools exist and where to find them, highlight opportunities for tool developement in the short and long term, and start a discussion about where to focus our time an

ayosec

BYTE UNIX Benchmarks

Summary

                                             c3.large           c4.large          c4 / c3
===========================================================================================
Dhrystone 2 using register variables       34752053.9 lps     43996767.0 lps       1.2660
Double-Precision Whetstone                     4459.8 MWIPS       8113.5 MWIPS     1.8193
Execl Throughput                               4110.8 lps         7697.1 lps       1.8724

ayosec

# Replace XXXXXXXXXXXXX with the VAT number
#
# The $valid attribute is in the path `soap:Body / checkVatResponse / valid`
#
# Example:
#
#   <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
#     <soap:Body>
#       <checkVatResponse xmlns="urn:ec.europa.eu:taxud:vies:services:checkVat:types">

ayosec

#!/usr/bin/ruby

require "tmpdir"

def usage()
  STDERR.puts <<EOU
Usage: #$0 input-file output-file ranges+

Ranges can be defined with:

ayosec

use std::collections::HashMap;
use std::collections::hash_map::Entry;

fn main() {
  let text = [
    "The", "quick", "brown", "fox", "jumped", "over", "the", "lazy", "dog",
    "at", "a", "restaurant", "near", "the", "lake", "of", "a", "new", "era"
  ];

  let mut map: HashMap<&str, u32> = HashMap::new();

ayosec

extern crate time;

#[deriving(Show)]
struct XorshiftStar {
  x: u64
}

impl XorshiftStar {
  fn new() -> XorshiftStar {
    XorshiftStar { x: time::now().tm_nsec as u64 }

ayosec

Benchmarks on different Map implementations for uint keys

Environment:

$ rustc --version
rustc 0.13.0-nightly (770378a31 2014-11-20 23:02:01 +0000)
$ uname -sm
Linux x86_64

No optimizations. No debug info