Yes - I intended that but never got time to implement it.

-- Gaby

| -----Original Message-----
| From: SG15 <sg15-bounces_at_[hidden]> On Behalf Of Olga Arkhipova
| via SG15
| Sent: Tuesday, August 27, 2019 10:13 AM
| To: ben.boeckel_at_[hidden]; Olga Arkhipova via SG15
| <sg15_at_[hidden]>; Cameron DaCamara
| <Cameron.DaCamara_at_[hidden]>
| Cc: Olga Arkhipova <olgaark_at_[hidden]>
| Subject: Re: [SG15] module source suffixes
|
| + Cameron
| Currently it builds (no ifc is produced), but I think it should be at least a
| warning.
| Olga
|
| -----Original Message-----
| From: Ben Boeckel <ben.boeckel_at_[hidden]>
| Sent: Tuesday, August 27, 2019 7:05 AM
| To: Olga Arkhipova via SG15 <sg15_at_[hidden]>
| Cc: Olga Arkhipova <olgaark_at_[hidden]>
| Subject: Re: [SG15] module source suffixes
|
| On Tue, Aug 27, 2019 at 03:49:16 +0000, Olga Arkhipova via SG15 wrote:
| > You still will be able to do it, but at least in MSVC case you'll have
| > to explicitly tell the compiler (by setting /module:interface switch)
| > that this cpp file is actually a module.
|
| Is this a mutually exclusive thing? Would saying `/module:interface` for a C++
| TU without `export module foo;` be a problem?
|
| --Ben
| _______________________________________________
| SG15 mailing list
| SG15_at_[hidden]
| https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.
| isocpp.org%2Fmailman%2Flistinfo.cgi%2Fsg15&amp;data=02%7C01%7Cgdr
| %40microsoft.com%7C66174e36458947ff961808d72b11e3f7%7C72f988bf8
| 6f141af91ab2d7cd011db47%7C1%7C0%7C637025228158409254&amp;sdat
| a=V7jBI1jUTE3OOotSmOhbtFylcYl3FTW3CfRyQIYv8B0%3D&amp;reserved=0