Multiple reactive plots towards a complete trader dashboard in D3
Copyright © 2015, Anil Nair - MIT License
var debug = process.env.NODE_ENV !== "production"; | |
var webpack = require('webpack'); | |
module.exports = { | |
context: __dirname, | |
devtool: debug ? "inline-sourcemap" : null, | |
entry: "./js/scripts.js", | |
output: { | |
path: __dirname + "/js", | |
filename: "scripts.min.js" |
import boto3 | |
session = boto3.Session( | |
aws_access_key_id="id", | |
aws_secret_access_key="secret", | |
region_name="us-east-1" | |
) | |
s3 = session.resource("s3") | |
obj = s3.Object("mybucket", "test.txt") |
package swaggerui | |
import ( | |
"net/http" | |
) | |
//go:generate go-bindata-assetfs -pkg=swaggerui -prefix=static/swagger-ui static/swagger-ui/dist/... | |
/* | |
Multiple reactive plots towards a complete trader dashboard in D3
Copyright © 2015, Anil Nair - MIT License
/* Composable errors via traits | |
A major challenge (among several) in error handling is how to deal with | |
disjoint error types produced by the libraries you use (as well as by | |
your own program) in a consistent and ergonomic way. Rust's `?` operator | |
improves the ergonomics of error handling, but it can only be used with | |
a single error type throughout a single function. Libraries define their | |
own error types and they don't know about each other, nor about the calling | |
program. So if we want to deal with errors from different libraries as | |
a single type (an sum or enum of the different underlying error types), we |
/* | |
Exercise about the Rust error handling. | |
Follow the instructions in the comments "Exercise" below. | |
References: | |
Book: https://doc.rust-lang.org/nightly/book/ch09-00-error-handling.html | |
Rust Standard Library: https://doc.rust-lang.org/stable/std/index.html | |
Crates IO: https://crates.io/ | |
random: https://rust-random.github.io/rand/rand/fn.random.html |
<style type="text/css"> | |
/****** EMAIL CLIENT BUG FIXES - BEST NOT TO CHANGE THESE ********/ | |
.ExternalClass { | |
width: 100%; | |
} | |
/* Forces Outlook.com to display emails at full width */ | |
.ExternalClass, .ExternalClass p, .ExternalClass span, .ExternalClass font, .ExternalClass td, .ExternalClass div { line-height: 100%; } | |
/* Forces Outlook.com to display normal line spacing, here is more on that: http://www.emailonacid.com/forum/viewthread/43/ */ | |