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.

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

Don't crash when calling gc() on a committed TyperState #13408

Merged
merged 1 commit into from
Aug 28, 2021

Commits on Aug 28, 2021

  1. Don't crash when calling gc() on a committed TyperState

    An already-committed TyperState might be committed again when errors are
    flushed (cf scala#12827, scala#13150) and `commit()` calls `gc()`. This operation
    could crash before this commit because we attempted to instantiate type
    variables no longer owned by the TyperState. We fix this by clearing
    `ownedVars` when committing a TyperState (because after committing it no
    longer owns any type variable).
    
    Fixes scala#13407.
    smarter committed Aug 28, 2021
    Configuration menu
    Copy the full SHA
    a040cc6 View commit details
    Browse the repository at this point in the history