scala - The Scala programming language

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add dummy javadoc typer and instrumentationwip-javadoc	Jakob Odersky	2016-06-22	1	-17/+73
\|
*	Fix javadoc position parsing	Jakob Odersky	2016-06-22	1	-19/+14
\|
*	Parse java comments in scaladoc	Jakob Odersky	2016-05-24	1	-28/+66
\|
*	it's Scaladoc, not "ScalaDoc" or "Scala doc"	Seth Tisue	2015-11-12	1	-2/+2
\| \| \| \| \|	renaming the existing ScalaDoc and ScalaDocReporter classes might break stuff, sadly, but at least we can fix the rest
*	Regularize `comment` hook method	Adriaan Moors	2014-07-17	1	-3/+4
\| \| \| \| \| \| \| \| \| \| \| \| \|	This is currently pretty borken, but let's at least not clutter innocent interfaces with this functionality. Moved `comment` (as `signalParsedDocComment`) next to the other hook methods in `Global`. For now, it calls the old `reporter.comment` hook method. As soon as the IDE is refactored to receive comments properly, the deprecated `Reporter#comment` method can be removed.
*	SI-8525 No anonymous lint	Som Snytt	2014-07-10	1	-1/+1
\| \| \| \| \| \| \| \| \|	Turn anonymous references to `settings.lint` into named settings. After that, trust to Adriaan to make them filterable. There are a few remaining top-level -Y lint warnings that are deprecated.
*	Rip out reporting indirection from CompilationUnit	Adriaan Moors	2014-07-04	1	-3/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Inline the forwarders from CompilationUnit, which should not affect behavior. Since all forwarders lead to global.reporter, don't first navigate to a compilation unit, only to then forward back to global.reporter. The cleanup in the previous commits revealed a ton of confusion regarding how to report an error. This was a mechanical search/replace, which has low potential for messing things up, since the list of available methods are disjoint between `reporter` and `currentRun.reporting`. The changes involving `typer.context` were done previously. Essentially, there are three ways to report: - via typer.context, so that reporting can be silenced (buffered) - via global.currentRun.reporting, which summarizes (e.g., deprecation) - via global.reporter, which is (mostly) stateless and straightforward. Ideally, these should all just go through `global.currentRun.reporting`, with the typing context changing that reporter to buffer where necessary. After the refactor, these are the ways in which we report (outside of typer): - reporter.comment - reporter.echo - reporter.error - reporter.warning - currentRun.reporting.deprecationWarning - currentRun.reporting.incompleteHandled - currentRun.reporting.incompleteInputError - currentRun.reporting.inlinerWarning - currentRun.reporting.uncheckedWarning Before: - c.cunit.error - c.enclosingUnit.deprecationWarning - context.unit.error - context.unit.warning - csymCompUnit.warning - cunit.error - cunit.warning - currentClass.cunit.warning - currentIClazz.cunit.inlinerWarning - currentRun.currentUnit.error - currentRun.reporting - currentUnit.deprecationWarning - currentUnit.error - currentUnit.warning - getContext.unit.warning - getCurrentCUnit.error - global.currentUnit.uncheckedWarning - global.currentUnit.warning - global.reporter - icls.cunit.warning - item.cunit.warning - reporter.comment - reporter.echo - reporter.error - reporter.warning - reporting.deprecationWarning - reporting.incompleteHandled - reporting.incompleteInputError - reporting.inlinerWarning - reporting.uncheckedWarning - typer.context.unit.warning - unit.deprecationWarning - unit.echo - unit.error - unit.incompleteHandled - unit.incompleteInputError - unit.uncheckedWarning - unit.warning - v1.cunit.warning All these methods ended up calling a method on `global.reporter` or on `global.currentRun.reporting` (their interfaces are disjoint). Also clean up `TypeDiagnostics`: inline nearly-single-use private methods.
*	SI-8407 "symbol not found" in Scaladoc use cases: warning only	Jason Zaugg	2014-03-13	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The refactoring in aedec1980 mistakenly used the non-silent typer to typecheck the use cases. It temptingly had the desired type (`ScalaDocAnalyzer`), but sadly the wrong properties (it will report errors, rather than buffer.) This meant that "symbol not found" errors in use cases would prevent Scaladoc generation. This commit introduces a little downcast on the silent typer. A more principled approach would be to go through the rigmarole of the virtual class pattern for `Analzyer.Typer`, but that will have to remain work for another day.
*	Updating Position call sites.	Paul Phillips	2013-09-27	1	-4/+4
\| \| \| \| \| \|	Calling position factories rather than instantiating these particular classes. Not calling deprecated methods. Added a few position combinator methods.
*	SI-7624 Fix a few remaining -Xlint warnings ...	Simon Ochsenreither	2013-08-15	1	-4/+2
\| \| \| \| \|	in various places. This includes actors, compiler (mostly some new macro parts) continuations, partest, scaladoc, scalap.
*	Eliminated the accumulated feature warnings.	Paul Phillips	2013-04-23	1	-19/+19
\| \| \| \| \| \| \| \| \|	No, this isn't busywork, how dare you suggest such a thing. I intend my tombstone to say HERE LIES EXTEMPORE, WHO ELIMINATED A LOT OF SIP-18 WARNINGS REST IN PEACE
*	SI-7376 Unmoored doc has correct position	Som Snytt	2013-04-17	1	-24/+17
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	The unmoored DocComment is created more eagerly so that its position is correct despite subsequent line comments. (Previously, skipComment would advance docPos.) It looks like the error caret is still off by one when a doc comment shows up in the middle of an operator, and who doesn't scaladoc the interior of expressions? Another bug fixed by Paul's refactor is that additional comments between the doc and the entity no longer breaks the scaladoc. Test added.
*	SI-7376 Scaladoc warns when discarding local doc comments with API tags	Som Snytt	2013-04-15	1	-2/+38
\| \| \| \| \| \| \| \| \| \| \| \| \|	Double-star doc comments in non-dockable positions at the end of a block will emit a warning only if API tags like @author are present, or under -Xlint. A real comment parser is applied early to probe for tags, to minimize ad hoc testing or duplication, but warnings are suppressed. Residual ad hockiness lies in precisely which tags to warn on. Ad hoc or ad doc. This fix is a stop gap; a richer solution would also report about other doc locations that won't be processed.
*	SI-7261 Implicit conversion of BooleanSetting to Boolean and BooleanFlag	Som Snytt	2013-03-27	1	-1/+1
\| \| \| \| \| \| \|	This commit shortens expressions of the form `if (settings.debug.value)` to `if (settings.debug)` for various settings. Rarely, the setting is supplied as a method argument. The conversion is not employed in simple definitions where the Boolean type would have to be specified.
*	Eliminated all forInteractive/forScaladoc uses.	Paul Phillips	2013-03-09	1	-0/+5
\| \| \| \| \| \| \| \|	This is the commit which brings it all together. The booleans forInteractive and forScaladoc are now deprecated and are not inspected for any purpose. All behavioral changes formerly accomplished via tests of those flags are embodied in the globals built specifically for those tasks.
*	Moved scaladoc code into src/scaladoc.	Paul Phillips	2013-03-09	1	-0/+229
	This leverages the preceding several commits to push scaladoc specific code into src/scaladoc. It also renders some scanner code more comprehensible.