Implement context validation on parse #2336
Open
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.
Contextual limitations are now performed at parse time.
This change was originally planned for version 3.4 but remained unaddressed.
I propose introducing it with the release of version 4.0.
Changes
Parser.parse_signature
.RBS::UnitTest
, they have not been removed in this PR.--[no-]exit-error-on-syntax-error
option.RBS::ParsingError
instead ofRBS::WillSyntaxError
.RBS::WillSyntaxError
.rbs validate
command have been stopped.CONST: self
in therbs prototype rb
.Not changes
RBS::ParsingError
is raised for compatibility with Steep. It may be possible to use a different error name.Parser.parse_type
andParser.parse_method_type
do not currently perform checks. It might be worth adding them.has_self_type?
,has_classish_type?
, andwith_nonreturn_void?
are used inRBS::UnitTest
, they have not been removed in this PR.