Per-function borrow checking misses top-level views of globals
If a language checks view/borrow liveness with a per-function CFG dataflow, a view (or address) bound at the top level to part of a mutable global escapes the check: function f replaces the global's element, while start() calls f() and then reads the view, so neither function's graph sees both the harm and the later use, giving a use-after-free that valgrind catches but the compiler accepts. The cheap sound fix is to forbid views/addresses as top-level bindings (as with other ownership modes that need a scope); the precise alternative is an interprocedural summary of which globals each function can harm. Also: when adding identity addresses for heap handles, the address's path must extend into the handle (element/deref step), since replacing the handle frees what the address names, unlike a view of the handle's slot which survives replacement.