Turn rich compiler errors on by default #2881
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tsloughter
approved these changes
Apr 11, 2024
ferd
force-pushed
the
use-rich-compiler-errors-by-default
branch
from
017fe3c
to
7208172
Compare
|
Been open for a month, got no extra review comments except those on the forums addressed here, merging it! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
They've been enabled almost a year ago since 3.22.0.
I've started gathering feedback on the Erlang Forums about it, and have been using it the whole time.
Once a long enough period has gone without any significant opposition, I'll merge this, with instructions on how to turn this off on the docs site.