diff options
author | Paul Phillips <paulp@improving.org> | 2013-04-08 08:30:49 -0700 |
---|---|---|
committer | Paul Phillips <paulp@improving.org> | 2013-04-08 13:29:23 -0700 |
commit | f986d6d6d703e1433923795fd5e9308a72f23459 (patch) | |
tree | 30a41a88e0d68d5b9a6cb3a63f358b45ac9cd8ba /docs | |
parent | c57c4f8c6227cff8ff9c1392428f97f036a34f2c (diff) | |
download | scala-f986d6d6d703e1433923795fd5e9308a72f23459.tar.gz scala-f986d6d6d703e1433923795fd5e9308a72f23459.tar.bz2 scala-f986d6d6d703e1433923795fd5e9308a72f23459.zip |
Reduce visibility of implicit class tags.
500 lines of generated boilerplate is *impossible to maintain*.
Generated code of this kind should never be allowed.
Three lines of documentation, duplicated 100 times, cannot
masquerade as three hundred lines of documentation. If someone
knows to look at the documentation of implicit ClassTags,
they *already know* about implicit ClassTags. It is wherever
"match" is documented which needs this information (and I am
sure we can express it more clearly, given the luxury of
only saying it once.)
Documenting each ClassTag with the same boilerplate is
comparable in utility to attaching such text to every Int.
"An Int is a whole number within the range -2147483648 to
2147483647 inclusive. It's usually used to represent how
many of something there are, such as '5 bunnies' or '3
witty commit messages', but you can store about anything
in an Int if you can fit it into 32 bits."
We don't do that, because you're expected to discover what
an Int is in a manner which generalizes to all the Ints you
may encounter. The situation with implicit ClassTags is
immediately analogous.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions