And, I am quite sure: BBasile = Basile Burg.

(Sorry no PR, I am on my phone in a hotel.)

On Tuesday, 20 February 2018 at 21:54:34 UTC, Bastiaan Veelo wrote:
> And, I am quite sure: BBasile = Basile Burg.
>
> (Sorry no PR, I am on my phone in a hotel.)

Yeah you're right Bastiaan, although for the NG i use a third variation.

On Tuesday, 20 February 2018 at 20:08:55 UTC, jmh530 wrote:
> On Tuesday, 20 February 2018 at 19:36:46 UTC, John Gabriele wrote:
>>
>> In:
>>
>>     import myModule : foo, bar;
>>
>> how do you know if bar is myModule.bar or if it's a separate module bar?
>
> It probably could be described a little better in the change log. It uses examples, but doesn't really describe what the file structure is that work with those examples.
>
> Perhaps this:
>
> --- pkg.d
> module pkg;
>
> public import pkg.mod1;
> public import pkg.mod2;
>
> --- pkg.mod1.d
> module pkg.mod1;
>
> enum sym1;
>
> --- pkg.mod2.d
> module pkg.mod2;
>
> enum sym2;
>
> If this structure works for both of those examples, then
> import pkg.mod1 : sym1, mod2 : sym2;
> works because mod2 has a selective import and
> import pkg.mod1 : sym1, sym2, pkg.mod2;
> works because pkg.mod2 is fully qualified (it may be annoying to find sym2 if this works with the above structure).

Thanks. Is the point to be able to string a bunch of selective imports together, as in:

    import pkg.mod1 : sym1, sym2, pkg.mod2 : sym1, sym2, pkg.mod3 : sym1;

?

That's difficult to read; it's hard to see the difference between the commas that separate the symbols vs the commas that separate the modules+symbols groups.

On Tue, Feb 20, 2018 at 10:19:03PM +0000, John Gabriele via Digitalmars-d-announce wrote: [...]
> Thanks. Is the point to be able to string a bunch of selective imports together, as in:
> 
>     import pkg.mod1 : sym1, sym2, pkg.mod2 : sym1, sym2, pkg.mod3 : sym1;
> 
> ?
> 
> That's difficult to read; it's hard to see the difference between the commas that separate the symbols vs the commas that separate the modules+symbols groups.

Yeah, personally I'd avoid writing it that way too.  But obviously enough people like this syntax to push it through. *shrug*


T

-- 
Nobody is perfect.  I am Nobody. -- pepoluan, GKC forum

On Tuesday, 20 February 2018 at 22:54:43 UTC, H. S. Teoh wrote:
> Yeah, personally I'd avoid writing it that way too.

There's no other way to use this feature though.

On Wednesday, February 21, 2018 10:04:01 Kagamin via Digitalmars-d-announce wrote:
> On Tuesday, 20 February 2018 at 22:54:43 UTC, H. S. Teoh wrote:
> > Yeah, personally I'd avoid writing it that way too.
>
> There's no other way to use this feature though.

Some of us think that it's a bad feature and have no intention of ever using it, though once it's in the language, we all have to worry about dealing with code that does use it.

- Jonathan M Davis

On Wednesday, 21 February 2018 at 10:15:48 UTC, Jonathan M Davis wrote:
> On Wednesday, February 21, 2018 10:04:01 Kagamin via Digitalmars-d-announce wrote:
>> On Tuesday, 20 February 2018 at 22:54:43 UTC, H. S. Teoh wrote:
>> > Yeah, personally I'd avoid writing it that way too.
>>
>> There's no other way to use this feature though.
>
> Some of us think that it's a bad feature and have no intention of ever using it, though once it's in the language, we all have to worry about dealing with code that does use it.
>
> - Jonathan M Davis

Was there a DIP for that?

/Paolo

On Tuesday, 20 February 2018 at 22:54:43 UTC, H. S. Teoh wrote:
> On Tue, Feb 20, 2018 at 10:19:03PM +0000, John Gabriele via Digitalmars-d-announce wrote: [...]
>> Thanks. Is the point to be able to string a bunch of selective imports together, as in:
>> 
>>     import pkg.mod1 : sym1, sym2, pkg.mod2 : sym1, sym2, pkg.mod3 : sym1;
>> 
>> ?
>> 
>> That's difficult to read; it's hard to see the difference between the commas that separate the symbols vs the commas that separate the modules+symbols groups.
>
> Yeah, personally I'd avoid writing it that way too.  But obviously enough people like this syntax to push it through. *shrug*
>
>

I also dislike this import syntax

On Wednesday, 21 February 2018 at 10:24:41 UTC, Paolo Invernizzi wrote:
> On Wednesday, 21 February 2018 at 10:15:48 UTC, Jonathan M Davis wrote:
>> On Wednesday, February 21, 2018 10:04:01 Kagamin via Digitalmars-d-announce wrote:
>>> On Tuesday, 20 February 2018 at 22:54:43 UTC, H. S. Teoh wrote:
>>> > Yeah, personally I'd avoid writing it that way too.
>>>
>>> There's no other way to use this feature though.
>>
>> Some of us think that it's a bad feature and have no intention of ever using it, though once it's in the language, we all have to worry about dealing with code that does use it.
>>
>> - Jonathan M Davis
>
> Was there a DIP for that?
>
> /Paolo

https://issues.dlang.org/show_bug.cgi?id=13855
https://github.com/dlang/dmd/pull/6589

On Wednesday, February 21, 2018 10:24:41 Paolo Invernizzi via Digitalmars-d- announce wrote:
> On Wednesday, 21 February 2018 at 10:15:48 UTC, Jonathan M Davis
>
> wrote:
> > On Wednesday, February 21, 2018 10:04:01 Kagamin via
> >
> > Digitalmars-d-announce wrote:
> >> On Tuesday, 20 February 2018 at 22:54:43 UTC, H. S. Teoh wrote:
> >> > Yeah, personally I'd avoid writing it that way too.
> >>
> >> There's no other way to use this feature though.
> >
> > Some of us think that it's a bad feature and have no intention of ever using it, though once it's in the language, we all have to worry about dealing with code that does use it.
>
> Was there a DIP for that?

No, and I have no idea whether Walter approved of it or knows anything about it. He may be fine with it, or it may be that another compiler dev merged it, and he didn't notice. The list of DIPs is here, and this definitely isn't one of them:

https://github.com/dlang/DIPs/tree/master/DIPs

When suggestions like this have come up in the past, some of us have been against the idea, and others have loved the idea, but until this beta was released, I had no idea that anyone had actually gone and implemented it.

- Jonathan M Davis