enforce scope shadowing statically with an extra phantom lifetime #13
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.
Fixes #11.
This API change tracks an additional lifetime parameter on a Scope representing the block in which the scope appears, and makes all the allocation API's require an &mut pointer to the scope. The nesting methods then freeze an outer scope so the allocation methods are statically prevented from using it while frozen. But because the allocation methods return a handle tied to the extra block lifetime, rather than the lifetime of the scope pointer itself, multiple allocations within a single block do not cause spurious borrow checker errors.
The net effect is that allocations do not require a dynamic check to enforce that they are not being performed on a Scope that is currently shadowed.