Skip to content

Lifetimes are unsuited as write lock identifiers #296

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

Closed
RalfJung opened this issue Aug 9, 2017 · 1 comment
Closed

Lifetimes are unsuited as write lock identifiers #296

RalfJung opened this issue Aug 9, 2017 · 1 comment

Comments

@RalfJung
Copy link
Member

RalfJung commented Aug 9, 2017

Analyzing the test failure in hashmap.rs revealed we have a problem with lifetime-based subtyping.
In insert_hashed_nocheck, _9 has type core::option::Option<collections::hash::map::Entry<ReScope(Remainder(BlockRemainder { block: NodeId(9681), first_statement_index: 0 })), K, V>> but then we have _17 = ((((_9 as Some).0 as Vacant).0, and _24 = _17, and _17 has type collections::hash::map::VacantEntry<ReScope(Misc(NodeId(9719))), K, V>. The lifetime changed.

@RalfJung
Copy link
Member Author

Actually it turns out that this is the same problem as the more fundamental "we can't identify write locks by their lifetime". Which is a problem in the model, not the implementation.

@RalfJung RalfJung changed the title Trouble with lifetime subtyping in validation Lifetimes are unsuited as write lock identifiers Aug 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant