There's a reason all these are specialized by hand but documenting each of them is beyond the point
Common conversion targets that affect any class in Scala
Set of classes to exclude from index and diagrams TODO: Should be configurable
The common context bounds and some humanly explanations.
The common context bounds and some humanly explanations. Feel free to add more explanations
<root>.scala.package.Numeric
is the type class
tparam
is the name of the type parameter it gets (this only describes type classes with 1 type param)
the function result should be a humanly-understandable description of the type class
Dirty, dirty, dirty hack: the value params conversions can all kick in -- and they are disambiguated by priority but showing priority in scaladoc would make no sense -- so we have to manually remove the conversions that we know will never get a chance to kick in.
Dirty, dirty, dirty hack: the value params conversions can all kick in -- and they are disambiguated by priority but showing priority in scaladoc would make no sense -- so we have to manually remove the conversions that we know will never get a chance to kick in. Anyway, DIRTY DIRTY DIRTY!
This is the hardcoded area of Scaladoc. This is where "undesirable" stuff gets eliminated. I know it's not pretty, but ultimately scaladoc has to be useful. :)