- review commit-by-commit
- checklist of revisions/questions that need to be taken care of
- rebasing will not delete comments
- ability to see only what's changed since the last time i looked at it
- persistent thumbs-up/thumbs down
- buttons to navigate next/prev commits
| // ---- | |
| // Sass (v3.4.14) | |
| // Compass (v1.0.3) | |
| // ---- | |
| div { | |
| margin: 0/0/0/0; | |
| padding: 0 / 0 / 0 / 0; | |
| } |
| ~/.rvm/gems/ruby-2.1.5@apangea $ grep -R "OpenSSL::Digest::Digest" . | |
| ./gems/aws-sdk-1.30.1/lib/aws/core/signature/version_4.rb: OpenSSL::HMAC.digest(OpenSSL::Digest::Digest.new('sha256'), key, value) | |
| ./gems/aws-sdk-1.30.1/lib/aws/core/signature/version_4.rb: OpenSSL::HMAC.hexdigest(OpenSSL::Digest::Digest.new('sha256'), key, value) | |
| ./gems/aws-sdk-1.30.1/lib/aws/core/signer.rb: OpenSSL::HMAC.digest(OpenSSL::Digest::Digest.new(digest), key, value) | |
| ./gems/aws-sdk-1.30.1/lib/aws/glacier/archive_collection.rb: digest = OpenSSL::Digest::Digest.new('sha256') | |
| ./gems/aws-sdk-1.30.1/lib/aws/glacier/archive_collection.rb: tree_digest = OpenSSL::Digest::Digest.new('sha256') | |
| ./gems/aws-sdk-1.30.1/lib/aws/glacier/archive_collection.rb: digest = OpenSSL::Digest::Digest.new('sha256') | |
| ./gems/fog-1.29.0/CHANGELOG.md:* Use OpenSSL::Digest instead of deprecated OpenSSL::Digest::Digest. *thanks Akira Matsuda* | |
| ./gems/jwt-0.1.8/lib/jwt.rb: private_key.sign(OpenSSL::Digest::Digest.n |
If you've ever had a memory leak, or watched a garbage collector run affect your application, but not been able to visualize and really understand what is happening, then this talk is for you. See examples, using physical objects, of how languages like C, Ruby, Rust, and others manage the memory that your code is using. Make the virtual into concrete things that can help you remember why it might be a problem to instantiate a new object in an embedded C program but not during a Rails request. Experience IRL how Rust's lifetimes eliminate the need for garbage collection as well as eliminating memory access errors that can happen in C. Be the reference counter you want to see in the world.
Carol (Nichols || Goulding)
Starting to contribute to open source can be overwhelming. The tips in this talk will help you find a path to contributing with less anxiety and confusion. Not sure what project to contribute to? Examine the OSS projects you use for recent activity, small open issues, and friendly maintainers. Not sure what to work on? Documentation, tests, and bug triaging are important contributions to open source that are much appreciated, often overlooked, and usually smaller in scope than a code change. Learn about Pull Request etiquette, what happens after you send in your work, and what it's like in a maintainer's shoes to take the mystery out of the process. Help make the open source world a better place!
https://s.gravatar.com/avatar/2ac88413948aad12e279e0d9609e7f74?s=300
Carol is currently the Hammer of Justice at Think Through Math in the lovely Pittsburgh, PA. She loves hugs, connecting people, Rust, Ruby, vinyl, percussion, home improve
| require 'minitest/autorun' | |
| class Poop < Minitest::Spec | |
| def subject | |
| {} | |
| end | |
| describe 'silliness' do | |
| it 'is an empty hash' do | |
| subject.must_equal {} |
| fn ansi_esc(input: &str) -> String { | |
| format!("\x1b[{}", input) | |
| } | |
| fn ansi_escape(message: &str) { | |
| let out = ansi_esc(message); | |
| // Use println to reproduce the issue | |
| println!("{}", out); | |
| // Use print to fix the issue | |
| // print!("{}", out); |
| options = Configuration.parse_options(ARGV) | |
| input_lines = $stdin.readlines | |
| File.open("/dev/tty", "r") do |in_file| | |
| File.open("/dev/tty", "w") do |out_file| | |
| tty = TTY.new(in_file, out_file) | |
| screen = Screen.new(tty) | |
| screen.tty.stty("-echo -icanon") | |
| config = Configuration.from_inputs(input_lines, options, screen.height) |
We will also have these on USB drives, but it would help if you install it early :)
When you have it installed, rustc --version should output rustc 0.13.0-nightly (ad9e75938 2015-01-05 00:26:28 +0000).
- Linux binaries (.tar.gz)
- Mac binaries (.tar.gz)
- 32-bit: https://static.rust-lang.org/dist/2015-01-05/rust-nightly-i686-apple-darwin.tar.gz
Thanks to @seejee for making this for me!!!
The goal of this is to have an easily-scannable reference for the most common syntax idioms in C# and Rust so that programmers most comfortable with C# can quickly get through the syntax differences and feel like they could read and write basic Rust programs.
What do you think? Does this meet its goal? If not, why not?