5 Commits

Author	SHA1	Message	Date
Chris Kipp	f90b09f1ee	feat: update Problem to account for related information and code ... This PR makes changes to the existing `xsbti.Problem` to account for an optional diagnostic code that the compiler can return for a given diagnostic and also related information. Given a piece of code like: ```scala try {} ``` You'll receive the following: ``` -- [E002] Syntax Warning: /Users/ckipp/Documents/scala-workspace/dotty-error-index/examples/002_EmptyCatchAndFinallyBlockID.scala:3:2 3 | try {} | ^^^^^^ | A try without catch or finally is equivalent to putting | its body in a block; no exceptions are handled. ``` The `E002` here is the actual code. Right now there would be no description. Some diagnostics have multiple positions that they need to represent. You can see an example of this [here](lampepfl/dotty#14002) in Dotty with the use of inlining. Instead of needing to rely on including all of that information in the diagnostic message it can now be extracted out into a `DiagnosticRelatedInformation`. These changes reference the conversation in #6868	2022-04-12 11:13:19 +02:00
Ethan Atkins	cf745255e8	Apply javafmt in sbt project	2020-01-14 14:38:08 -08:00
Ethan Atkins	ad59e71b1a	Add util headers ... None of the util files had headers.	2019-12-08 10:29:22 -08:00
Guillaume Martres	15522a0cbe	Add Problem#rendered to customize how problems are shown ... Dotty has its own logic for displaying problems with the proper file path, position, and caret, but if we store this information in Problem#message we end up with duplicated information in the output since Zinc will prepend/append similar things (see sbt.internal.inc.ProblemStringFormats). So far, we worked around this in Dotty by using an empty position in the sbt bridge reporter, but this means that crucial semantic information that could be used by a Build Server Protocol implementation and other tools is lost. This commit allows us to avoid by adding an optional `rendered` field to `Problem`: when this field is set, its value controls what the user sees, otherwise we fallback to the default behavior (the logic to do this will be added to Zinc after this PR is merged and a new release of sbt-util is made).	2018-08-28 03:58:15 +09:00
Eugene Yokota	871b4f4eef	move modules around.	2015-08-20 00:59:57 -04:00