<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 19 Aug 2020 at 23:18, Artem Dergachev <<a href="mailto:noqnoqneo@gmail.com">noqnoqneo@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
Gabor, we've talked about this two days ago >_><br></div></blockquote><div> </div><div>This email is much easier to follow than a verbal discussion :D Now I have a much better understanding of what you meant.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<br>
I believe we should remove SymbolConjured's identity elements from
SymbolMetadata and instead make it work more like SymbolRegionValue
works in RegionStore. Namely:<br></div></blockquote><div><br></div><div>If SymbolMetadata works like SymbolRegionValue, do we actually need both? I mean I do understand that we use them for different purposes, but we could also have a type alias or something like that if that actually helps understanding how the analyzer works.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<br>
2. Get rid of the metadata-in-use set. From now on SymbolMetadata,
like SymbolRegionValue, is live whenever its region is live.<br></div></blockquote><div><br></div><div>Will this work for code examples where the actual string is already dead but we still want to compute with its length? <br></div><div> </div></div></div>