The Sorbet syntax for type annotations representing arrays, hash maps, and other containers defined in the Ruby standard library looks different from other [class types](/docs/class-types) despite the fact that Ruby uses classes to represent these values, too. Here's the syntax Sorbet uses:| sorbet.org
Classes are also values in Ruby. Sorbet has two ways to describe the type of these class objects: `T.class_of(...)` and `T::Class[...]`.| sorbet.org
| sorbet.org
Sorbet does not allow generic methods to have non-generic default arguments. The best alternative is to split the method into two methods, with one implemented by calling the other with the default value.| blog.jez.io
There's a neat trick for using generic methods to get around some of the limitations that invariant type members in generic classes carry.| blog.jez.io
Abstract singleton class methods do not belong in a well-behaved type system. Sorbet allows them anyways, which causes problems. Here's why they're bad and what to do instead.| blog.jez.io
`T.attached_class` can be used to refer to the type of instances from a| sorbet.org
Sorbet supports method override checking. These checks are implemented as `sig`| sorbet.org
Intersection types are how we overlap two types, declaring that an expression| sorbet.org
The straightforward attempt at writing a Sorbet signature for a method that calls `klass.new` doesn't work. The strategy that does work uses abstract methods, and so I'd like to walk through an extended example showing how to get such code to typecheck.| blog.jez.io