fix: error on super[key] when there is no superclass#911
Open
He-Pin wants to merge 1 commit into
Open
Conversation
Motivation: visitLookupSuper (super[key]) silently fell back to self when no superclass existed, while visitSelectSuper (super.name) correctly reported "Attempt to use `super` when there is no super class". This inconsistency could mask bugs in Jsonnet programs and diverged from go-jsonnet and jrsonnet which both error in this case. Modification: Replace the silent `sup = self` fallback in visitLookupSuper with the same error that visitSelectSuper uses. Change `var sup` to `val sup` since it is no longer reassigned. Result: super[key] and super.name now behave identically when there is no superclass, both reporting the same error. This matches go-jsonnet and jrsonnet semantics.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
visitLookupSuper(super[key]) to error when there is no superclass, matching the existingvisitSelectSuper(super.name) behavior.Motivation
visitLookupSuper(super[key]) silently fell back toselfwhen no superclass existed, whilevisitSelectSuper(super.name) correctly reported"Attempt to use \super` when there is no super class"`. This inconsistency could mask bugs in Jsonnet programs and diverged from go-jsonnet and jrsonnet which both error in this case.Modification
Replace the silent
sup = selffallback invisitLookupSuperwith the same error thatvisitSelectSuperuses. Changevar suptoval supsince it is no longer reassigned.Result
super[key]andsuper.namenow behave identically when there is no superclass, both reporting the same error. This matches go-jsonnet and jrsonnet semantics.Test plan