Skip to content

Conversation

@WojciechMazur
Copy link
Contributor

@WojciechMazur WojciechMazur commented Dec 11, 2025

Resolves #24720

Piggy backs fixes that would be required to have correct assertions in generated scaladoc (would be most likelly cherry-picked before merge):

  • allow to specific sc-opts:<scala-options>* to pass specify scalacOptions that would be passed to the snippetCompiler
  • show position of snippets that failed to compile

TODO:

  • - error codes 101-222
  • - document 11 inactive error codes - if inactive after 3.0.0 add latest stable release emitting errors
  • - setup CI assertions to ensure all snippets emit correct error - E001.md should emit only [E001] errors etc.
  • - for error codes introduced after 3.0.0 add information about version when given error was introduced

@WojciechMazur
Copy link
Contributor Author

Rendered examples:
image
image

@bishabosha
Copy link
Member

is there an automated process to check for addition of new error codes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create a documentation of compiler error codes

2 participants