C++ Logo


Advanced search

Re: [Tooling] Modules naming

From: JF Bastien <cxx_at_[hidden]>
Date: Thu, 10 Jan 2019 12:40:29 -0800
On Thu, Jan 10, 2019 at 12:24 PM Rene Rivera <grafikrobot_at_[hidden]> wrote:
> On Thu, Jan 10, 2019 at 11:47 AM JF Bastien <cxx_at_[hidden]> wrote:
>> On Thu, Jan 10, 2019 at 6:53 AM Corentin <corentin.jabot_at_[hidden]> wrote:
>> >
>> > Hello.
>> > I would like to suggest two modules related proposals that I think SG15 should look at.
>> >
>> > - Compiler enforced mapping between module names and module interface file (resource) name.
>> Why does SG15 need to do this, versus someone implementing it in an
>> open-source toolchain, trying it out, and bringing what using it
>> taught them to SG15?
> 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?

Sure, tell people why this "no" vote is useful, and they'll vote in
that direction. Why do you think blocking merging modules to the IS is
desirable? What is needed to unblock the merge?

Received on 2019-01-10 21:40:42