<div dir="ltr"><div dir="ltr"><div>Dear SG15,<br><br></div> To address one of the previous concerns, I've made sure to specifically add a call out a new Word of Power in this proposal: <a href="https://thephd.github.io/vendor/future_cxx/papers/d1130.html#wording-intent">https://thephd.github.io/vendor/future_cxx/papers/d1130.html#wording-intent</a>. It's called <i>resource-location</i> or <i>resource-locations</i>. This will give std::embed and other proposals a well-defined way of referring to a lookup mechanism. It is still implementation-defined where this comes from, but just like include paths I expect this to come from a Resource Path command line parameter that build systems can tap into.</div><div dir="ltr"><br></div><div> If you have any other concerns or questions, please do let me know!<br><br></div><div>Sincerely,<br></div><div>JeanHeyd Meneide<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Dec 3, 2018 at 6:13 AM JeanHeyd Meneide <<a href="mailto:phdofthehouse@gmail.com">phdofthehouse@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>> That's insufficient: to be usable, it must also say that it is<br>> *the same* for all resource strings, regardless of which facility<br>
> (std::embed, etc) they are used in.
<br><br>Resource lookup will be exactly what is written in this paper, so long as I can get consensus and move this through the Committee.
As the author of std::embed, I have the privilege of moving these papers in sync. Should p1130 be accepted, std::embed will be updated to specifically call out Resource Lookup, as defined in [module.requires] (or whatever it ends up being).<br></div></div>
</blockquote></div>