Simon Zünd bdfd1e4b38 [torque] More flexibel and uniform error reporting ... This CL changes the existing TorqueError struct into a more general TorqueMessage by adding a "kind" enum. The contextual for lint errors is removed and replaced by a list of TorqueMessages. A MessageBuilder is introduced to help with the different combinations of present information and method of reporting. A lint error with custom SourcePosition can be reported like this: Lint("naming convention error").Position(<src_pos_var>); While a fatal error, with CurrentSourcePosition can be thrown like this: Error("something went horrible wrong").Throw(); This approach is both backwards compatible and should prove flexible enough to add more information to messages or add other message kinds. Bug: v8:7793 Change-Id: Ib04fa188e34b3e8e9a6526a086f80da8f690a6f5 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1617245 Commit-Queue: Simon Zünd <szuend@chromium.org> Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Reviewed-by: Sigurd Schneider <sigurds@chromium.org> Cr-Commit-Position: refs/heads/master@{#61696}		2019-05-21 13:26:08 +00:00
..
earley-parser-unittest.cc	[torque] add unittest for Earley parser	2018-07-24 14:01:33 +00:00
ls-json-unittest.cc	Reland^3 "[torque] Throw exception instead of aborting if something goes wrong"	2019-04-16 10:41:20 +00:00
ls-message-unittest.cc	[torque] More flexibel and uniform error reporting	2019-05-21 13:26:08 +00:00
ls-server-data-unittest.cc	[torque] check runtime function signatures properly	2019-05-14 13:35:32 +00:00
torque-unittest.cc	[torque] More flexibel and uniform error reporting	2019-05-21 13:26:08 +00:00
torque-utils-unittest.cc	[torque-ls] fix Windows file paths	2019-04-24 08:17:07 +00:00