summaryrefslogtreecommitdiff
path: root/src/library/scala/annotation/elidable.scala
Commit message (Collapse)AuthorAgeFilesLines
* Remove unused imports and other minor cleanupsSimon Ochsenreither2015-12-181-3/+1
| | | | | | | | | | - Language imports are preceding other imports - Deleted empty file: InlineErasure - Removed some unused private[parallel] methods in scala/collection/parallel/package.scala This removes hundreds of warnings when compiling with "-Xlint -Ywarn-dead-code -Ywarn-unused -Ywarn-unused-import".
* Brings all copyrights (in comments) up-to-date, from 2011/12 to 2013Heather Miller2012-11-021-1/+1
|
* Eliminate breaking relative names in source.Paul Phillips2012-09-141-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These things are killing me. Constructions like package scala.foo.bar.baz import foo.Other DO NOT WORK in general. Such files are not really in the "scala" package, because it is not declared package scala package foo.bar.baz And there is a second problem: using a relative path name means compilation will fail in the presence of a directory of the same name, e.g. % mkdir reflect % scalac src/reflect/scala/reflect/internal/util/Position.scala src/reflect/scala/reflect/internal/util/Position.scala:9: error: object ClassTag is not a member of package reflect import reflect.ClassTag ^ src/reflect/scala/reflect/internal/util/Position.scala:10: error: object base is not a member of package reflect import reflect.base.Attachments ^ As a rule, do not use relative package paths unless you have explicitly imported the path to which you think you are relative. Better yet, don't use them at all. Unfortunately they mostly work because scala variously thinks everything scala.* is in the scala package and/or because you usually aren't bootstrapping and it falls through to an existing version of the class already on the classpath. Making the paths explicit is not a complete solution - in particular, we remain enormously vulnerable to any directory or package called "scala" which isn't ours - but it greatly limts the severity of the problem.
* Address doc comment rot in the standard library.Jason Zaugg2012-05-131-2/+6
| | | | | | | | | | | | | | | | | | | | | - Match @param/@tparam names to the actual parameter name - Use @tparam for type parameters - Whitespace is required between `*` and `@` - Fix incorrect references to @define macros. - Use of monospace `` and {{{}}} (much more needed) - Remove `@param p1 ...` stubs, which appear in the generated docss. - But, retainsed `@param p1` stubs, assuming they will be filtered from the generated docs by SI-5795. - Avoid use of the shorthand `@param doc for the solitary param` (which works, but isn't recognized by the code inspection in IntelliJ I used to sweep through the problems) The remaining warnings from `ant docs` seem spurious, I suspect they are an unintended consequence of documenting extension methods. [scaladoc] /Users/jason/code/scala/src/library/scala/collection/TraversableOnce.scala:181: warning: Variable coll undefined in comment for method reduceOption in class Tuple2Zipped [scaladoc] def reduceOption[A1 >: A](op: (A1, A1) => A1): Option[A1] = reduceLeftOption(op) [scaladoc] ^
* Whitespace commit.Paul Phillips2012-02-291-2/+2
| | | | | | | Removed all the trailing whitespace to make eugene happier. Will try to keep it that way by protecting at the merge level. Left the tabs in place because they can't be uniformly changed to spaces, some are 2, some are 4, some are 8, whee.
* Fleshed out the @elidable documentation.Paul Phillips2012-02-231-15/+43
|
* update api docs for @elidable to match the behaviour more closely.Szabolcs Berecz2012-02-231-4/+7
|
* 2nd round of clean ups (see r25285)michelou2011-07-151-12/+15
|
* Updated copyright notices to 2011Antonio Cunei2011-01-201-1/+1
|
* Some modifications to @elidable: for reasons lo...Paul Phillips2011-01-121-12/+27
| | | | | | | | Some modifications to @elidable: for reasons lost to me now it had a default value such that annotated methods might be elided even if the option wasn't given. It now does nothing in that situation. Closes #4051, #4151, no review.
* Moved ClassfileAnnotation/StaticAnnotation/Anno...Paul Phillips2010-12-061-1/+1
| | | | | | | Moved ClassfileAnnotation/StaticAnnotation/Annotation/TypeConstraint into scala.annotation and enabled the deprecated type aliases in scala.* to point there. Also enclosed is a new starr to bootstrap. No review.
* Although it was working fine, a test case for @...Paul Phillips2010-03-231-2/+2
| | | | | | Although it was working fine, a test case for @elidable to make sure that state of affairs continues. No review.
* Fixed a number of faulty Scaladoc comments in l...Gilles Dubochet2010-01-261-2/+2
| | | | | | Fixed a number of faulty Scaladoc comments in library and compiler sources. No review.
* Updated copyright notices to 2010Antonio Cunei2009-12-071-1/+1
|
* add @since scaladoc tag to scala.annotation.*stepancheg2009-09-261-0/+4
|
* Generalized -Xdisable-assertions into an annota...Paul Phillips2009-09-091-0/+64
Generalized -Xdisable-assertions into an annotation (presently called @elidable) so it can be used with arbitrary code. It takes an argument which sets its priority level, and you can control what code is elided from the command line by setting -Xelide-level to desired threshold.