Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Properly handle the case where SpecializeType() returns an error `S… #53990

Merged
merged 1 commit into from Jan 26, 2022
Merged

Properly handle the case where SpecializeType() returns an error `S… #53990

merged 1 commit into from Jan 26, 2022
+4 −1

Commits on Jan 25, 2022

  1. Properly handle the case where SpecializeType() returns an error `S… 

    …tatus`.

If the error case in `SpecializeType()` is reached, then we would get a crash when trying to access the value of an errorenous `StatusOr` object

PiperOrigin-RevId: 408380069
Change-Id: If3c3fc876dcf9384d5ec7a4985adc68c23ea7318
    @mihaimaruseac @pranve
    mihaimaruseac authored and pranve committed Jan 25, 2022
    Configuration menu
    Copy the full SHA
    5a457df View commit details
    Browse the repository at this point in the history