-
Notifications
You must be signed in to change notification settings - Fork 15.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Prohibit using features in the same file they're defined in.
This is an edge case we can't handle properly today. Rather than allowing poorly defined behavior, we'll make this an error condition until we can actually support it. In the future, it may be necessary to upgrade feature files to newer editions. Closes #16756 PiperOrigin-RevId: 634512378
- Loading branch information
1 parent
baeab50
commit 24b91a7
Showing
2 changed files
with
70 additions
and
16 deletions.
There are no files selected for viewing
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
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
@mkruskal-google, the error below looks to be triggered from line 10383 above. Maybe you could add another test case with an option that instead uses a message literal, like this one? It doesn't look like this change handles this. I think this would need to be a post-process after unmarshalling the uninterpreted aggregate value, to look for any extension fields that were defined in the same file.