search for: uniquablemdnod

...ssential to refer to global variables etc. That said, I think that it will eventually be worthwhile to have metadata versions of integers and other common things to reduce memory. This should come in a later pass of course. Yup, agree entirely. > > I don’t follow the point of > +class UniquableMDNode : public MDNode { > > What would subclass it? What is the use-case? Won’t MDStrings continue to be uniqued? I think you've just been misled by my terrible name. This sketch splits the "temporary" concept for `MDNode` into a separate subclass, so that non-forward-reference...

TL;DR: If you use metadata (especially if it's out-of-tree), check the numbered list of lost functionality below to see whether I'm trying to break your compiler permanently. In response to my recent commits (e.g., [1]) that changed API from `MDNode` to `Value`, Eric had a really interesting idea [2] -- split metadata entirely from the `Value` hierarchy, and drop general support for