<div dir="ltr"><div dir="ltr">On Thu, Jan 10, 2019 at 11:47 AM JF Bastien <<a href="mailto:cxx@jfbastien.com">cxx@jfbastien.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Jan 10, 2019 at 6:53 AM Corentin <<a href="mailto:corentin.jabot@gmail.com" target="_blank">corentin.jabot@gmail.com</a>> wrote:<br>
><br>
> Hello.<br>
> I would like to suggest two modules related proposals that I think SG15 should look at.<br>
><br>
> - Compiler enforced mapping between module names and module interface file (resource) name.<br>
<br>
Why does SG15 need to do this, versus someone implementing it in an<br>
open-source toolchain, trying it out, and bringing what using it<br>
taught them to SG15?</blockquote><div><br></div><div>Are we willing to vote NO on merging modules to the IS until we do such an implementation and wait for build system and dependency management implementation experience?</div><div> </div></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr">-- Rene Rivera<br>-- Grafik - Don't Assume Anything<br>-- Robot Dreams - <a href="http://robot-dreams.net/" target="_blank">http://robot-dreams.net</a><br><br></div></div></div></div></div>