std
Aliases for types I've had to import over and over and over again.
Aliases for types I've had to import over and over and over again. Your list may vary.
Hand specialized on the left, @specialized on the right, value classes for tuple creation.
The classic type class for encoding value equivalence.
Various lame global-scope implicits, made to disappear with our friend null.
Various lame global-scope implicits, made to disappear with our friend null. This list is subject to renegotiation.
A valid index is always non-negative.
A valid index is always non-negative. All negative indices are mapped to NoIndex, which has an underlying value of -1. In principle we could double the usable range by treating value as an unsigned Int other than -1.
All IndexRanges are inclusive of start and exclusive of end.
A one-based index.
A one-based index. In principle Index(n) and Nth(n + 1) have the same behavior for all values n >= 0, assuming things type check. I resist cosmetic implicits.
Unlike an Index, an Offset can have any integer value.
Unlike an Index, an Offset can have any integer value. A negative offset is a positive offset from the other reference point.
An immutable Map with a fixed iteration order.
An immutable Map with a fixed iteration order. It's not a "sorted" map since it has no ordering. It's true one could say its ordering is Ordering[Int] on indexOf. Maybe that will seem like a good idea at some point.
Yes I know all about implicit classes.
Yes I know all about implicit classes. There's no way to write an implicit value class which doesn't hardcode its location into an object. Separating the implicit conversion from the class allows clients to build their own package object.
This is all a consequence of scala offering no means for managing namespaces, so namespace management has become hopelessly entangled with unrelated concerns like inheritance, specificity, method dispatch, and so forth.
Rather than struggle with ambiguities with Predef.augmentString, we'll bury it and reimplement what we want.
We could avoid this duplication with some of scala's incredibly high-cost (in performance and complexity tax) machinery.
We could avoid this duplication with some of scala's incredibly high-cost (in performance and complexity tax) machinery. I'll take the duplication at this point.
The classic type class for encoding string representations.
When a type class is more trouble than it's worth.
When a type class is more trouble than it's worth. Not overriding toString here to leave open the possibility of using a synthetic toString, e.g. of case classes.
Used to achieve type-safety in the show interpolator.
Used to achieve type-safety in the show interpolator. It's the String resulting from passing a value through its Show instance.
It's like "" + x, except, you know, for kids.
It's like "" + x, except, you know, for kids.
These methods arrived in jl.{ Integer, Long } in java7.