4 Commits (a0149872ad1670325855dcaceb08b8de79132891)

Author	SHA1	Message	Date
Sam Blackshear	a0149872ad	[ownership] report invocation of lambdas capturing a var whose lifetime is over ... Summary: If a `Closure` expression `e` captures variable `x`, consider `e` as borrowing from `x`. When the closure is invoked via `operator()`, check that the borrow is still valid. Reviewed By: jeremydubreil Differential Revision: D7071839 fbshipit-source-id: d923a6a	7 years ago
Sam Blackshear	58adf8dd52	[ownership] implementing borrowing ... Summary: Fairly simple approach here: - If the RHS of an assignment is a frontend-generated temporary variable, assume it transfers ownership to the LHS variable - If the RHS of an assignment is a program variable, assume that the LHS variable is borrowing from it. - If we try to access a variable that has borrowed from a variable that is now invalid, complain. Reviewed By: jeremydubreil Differential Revision: D7069947 fbshipit-source-id: 99b8ee2	7 years ago
Sam Blackshear	4485e97bee	[ownership] report use after destructor ... Summary: Similar to use-after-`delete`. Reviewed By: jeremydubreil Differential Revision: D7032893 fbshipit-source-id: a974dc3	7 years ago
Sam Blackshear	d76d20a9ca	[ownership] prototype of ownership analysis for tracking reads/moves ... Summary: A simple intraprocedural analysis that tracks when a storage location is read or deleted. For now, this works only with local variable storage locations; field and array accesses are ignored. In order to test this, I added a new "use-after-lifetime" warning. It complains when a variable is read or deleted after it has already been deleted. Reviewed By: jeremydubreil Differential Revision: D6961314 fbshipit-source-id: 75e95a2	7 years ago