@6d7a Thanks for the PR! I didn't understand how your patch addresses the problem. If I understand correctly, the problem is that TAG_TREE and VARIANT_TAG_TREE will get same address which will break things (here, and probably in other places too) but I'm not sure how this PR prevents that and how well it generalize to other cases.

In addition to that bug which we need to fix, infinite constants might exist, so we might need to add a depth limit or something like that to the create_memory_map function.

@HKalbasi thank you for your review. My reasoning in case of the fix was to prevent that reference values point to the location that they themselves reside in. However I can see that this is more of a hotfix for my particular case instead of a sustainable solution. Too much wishful thinking on my part.
I have removed the fix and added a stack depth check by propagating the Evaluator's stack depth limit along the call chain of create_memory_map. That prevents a terminal stack overflow, which makes rust-analyzer impossible to use in certain projects, and instead returns a soft internal error. I adapted the test accordingly.
I'd be interested in finding a way to better handle recursive const cases, though, but I guess that's for another PR.

Thanks!
@bors r+

I'd be interested in finding a way to better handle recursive const cases, though, but I guess that's for another PR.

AFAIK there is no way to create infinite constants in stable Rust, so this is good for now.

Though we should find out why it is allocating the same address for different constants, as it can cause problems even without recursive types.

📌 Commit 142ef76 has been approved by HKalbasi

It is now in the queue for this repository.

⌛ Testing commit 142ef76 with merge 3dfd4c1...

☀️ Test successful - checks-actions
Approved by: HKalbasi
Pushing 3dfd4c1 to master...