My notes from implementing Job Vranish's excellent guide.
Follow along with the guide above, getting rustc from rustup or similar:
rustc 1.0.0-nightly (dcaeb6aa2 2015-01-18 11:28:53 +0000)
binary: rustc
commit-hash: dcaeb6aa23ecba2dc2af870668a9239136d20fa3
commit-date: 2015-01-18 11:28:53 +0000
| /** | |
| * USL - Useless Stack Language | |
| */ | |
| import scala.collection.mutable | |
| object USL { | |
| /******************** | |
| * Handling USL Data | |
| ********************/ |
| {-# LANGUAGE GADTs #-} | |
| module Yolo where | |
| import System.IO.Unsafe | |
| class Yolo f where | |
| yolo :: f a -> a | |
| instance Yolo Maybe where | |
| yolo (Just x) = x |
| .SILENT: | |
| .PHONY: help | |
| # Based on https://gist.github.com/prwhite/8168133#comment-1313022 | |
| ## This help screen | |
| help: | |
| printf "Available targets\n\n" | |
| awk '/^[a-zA-Z\-\_0-9]+:/ { \ | |
| helpMessage = match(lastLine, /^## (.*)/); \ |
| package scalax.collection | |
| import scala.collection.mutable.ListBuffer | |
| /** FoldTransformers and the views based on them are a Scala | |
| * adaptation, and to some degree an extension, of Rich Hickey's | |
| * transducers for Clojure. They show that the concepts can be | |
| * implemented in a type-safe way, and that the implementation is | |
| * quite beautiful. | |
| */ | |
| object FoldingViews { |
| import annotation.unchecked.uncheckedVariance | |
| /** The trait of things that can be compared safely */ | |
| trait Equals[-T] { | |
| /** A witness of Equals' type parameter. Should only used for | |
| * the constraint in EqlDecorator, hence, @uncheckedVariance should not be a problem. | |
| */ | |
| type EqualsDomain = T @uncheckedVariance |
| class ClobberTable<K, T> { | |
| ClobberTable parent; | |
| HashTable<K, T> my; | |
| ArrayList<K> whites; | |
| public ClobberTable() { | |
| parent = null; | |
| my = new HashTable<K, T>(); | |
| whites = new ArrayList<K>(); | |
| } |
... or Why Pipelining Is Not That Easy
Golang Concurrency Patterns for brave and smart.
By @kachayev
| 141.195.91.37 |
| # Scaladoc Developer Guide | |
| ## Introduction | |
| Scaladoc is the tool that enables developers to automatically generate documentation for their Scala (and Java) projects. It is Scala's equivalent of the widely-used Javadoc tool. This means that Javadoc (and even doxygen) users will be familiar with Scaladoc from day 1: for them, it is most beneficial to check out the Scaladoc/Javadoc comparison tables and if necessary, skim through this document to understand specific features. | |
| The rest of this tutorial is aimed at developers new to Scaladoc and other similar tools. It assumes a basic understanding of the Scala language, which is necessary to follow the examples given throughout the tutorial. For the user perspective on the Scaladoc-generated documentation, such as finding a class, understanding the page layout, navigating through diagrams, please refer to the Scaladoc User Guide. | |
| The tutorial will start by a short motivation and then will explain the main concept in Scaladoc: the doc comment. | |
| ### Why document? |
