Re: const(Rvalue) resolved to different overloads

2016-12-30 Thread Jonathan M Davis via Digitalmars-d
On Thursday, December 29, 2016 14:54:35 Ali Çehreli via Digitalmars-d wrote: > I'm working on understanding how different qualifiers of the same type, > the kinds of indirections that its members may have, and the expressions > being lvalue versus rvalue affect function overload resolution. > > For

[your code here]

2016-12-30 Thread Joseph Agiri via Digitalmars-d
Why is the compiler for the D language not downloading from your site. It has not enabled me to be entirely fascinated with the language with confidence. Please correct the challenge. Does it have issues with Windows 7?

Re: [your code here]

2016-12-30 Thread Bauss via Digitalmars-d
On Friday, 30 December 2016 at 08:17:54 UTC, Joseph Agiri wrote: Why is the compiler for the D language not downloading from your site. It has not enabled me to be entirely fascinated with the language with confidence. Please correct the challenge. Does it have issues with Windows 7? The com

Re: D Future...

2016-12-30 Thread keito940 via Digitalmars-d
If you improve the standard library, everything OK? If... Next Version Request. Add To The F Sharp Like Pipeline Operator(D Language Pipeline Syntax is BAD.) & SML(C Language Compatible) Like Function Syntax &Haskell Like Maybe Monad&Binary Execution speed Up. Plz,Now!!!

Re: D future ...

2016-12-30 Thread keito940 via Digitalmars-d
On Tuesday, 20 December 2016 at 01:45:27 UTC, Tommi wrote: Improve the standard library! ...If you improve the standard library, everything OK? If... Next Version Request. Add To The F Sharp Like Pipeline Operator(D Language Pipeline Syntax is BAD.) & SML(C Language Compatible) Like Function S

Re: D future ...

2016-12-30 Thread aberba via Digitalmars-d
On Friday, 30 December 2016 at 06:22:40 UTC, bauss wrote: [...] Yeah. I meant a subset. But widgets will not follow the DOM query syntax, it should use class attributes. .button { border-color: red; } .container { ... } auto btn = new Button(); btn.addClass("button"); btn.addStyleFromF

Re: D future ...

2016-12-30 Thread Bauss via Digitalmars-d
On Friday, 30 December 2016 at 11:32:50 UTC, aberba wrote: On Friday, 30 December 2016 at 06:22:40 UTC, bauss wrote: [...] Yeah. I meant a subset. But widgets will not follow the DOM query syntax, it should use class attributes. .button { border-color: red; } .container { ... } auto b

Re: D future ...

2016-12-30 Thread Bauss via Digitalmars-d
On Friday, 30 December 2016 at 13:26:15 UTC, Bauss wrote: On Friday, 30 December 2016 at 11:32:50 UTC, aberba wrote: [...] Yeah it kinda follows classes right now already. It follows a little different concept, where it's based on selectors and not classes. So you give your component selec

Bitfields?

2016-12-30 Thread Martin via Digitalmars-d
Are there any C-like bitfields in D? Yes - How can I use them? No - What could be used in their stead?

Re: D future ...

2016-12-30 Thread Getald via Digitalmars-d
On Thursday, 29 December 2016 at 21:41:45 UTC, aberba wrote: Styling is similar to CSS but different. Wished someone would just go for a full blown CSS parser. CSS has proven its more capable and loved for client side styling/decoration. Isn't this what GTK is essentially doing already where

Re: D future ...

2016-12-30 Thread Bauss via Digitalmars-d
On Friday, 30 December 2016 at 13:56:30 UTC, Getald wrote: On Thursday, 29 December 2016 at 21:41:45 UTC, aberba wrote: Styling is similar to CSS but different. Wished someone would just go for a full blown CSS parser. CSS has proven its more capable and loved for client side styling/decoratio

Re: Bitfields?

2016-12-30 Thread Marc Schütz via Digitalmars-d
On Friday, 30 December 2016 at 13:45:23 UTC, Martin wrote: Are there any C-like bitfields in D? Yes - How can I use them? No - What could be used in their stead? Not built-in, but in the standard library: https://dlang.org/phobos/std_bitmanip.html#.bitfields

Re: D Future...

2016-12-30 Thread Bauss via Digitalmars-d
On Friday, 30 December 2016 at 09:49:27 UTC, keito940 wrote: If you improve the standard library, everything OK? If... Next Version Request. Add To The F Sharp Like Pipeline Operator(D Language Pipeline Syntax is BAD.) & SML(C Language Compatible) Like Function Syntax &Haskell Like Maybe Monad&

Re: Bitfields?

2016-12-30 Thread Martin via Digitalmars-d
On Friday, 30 December 2016 at 14:06:06 UTC, Marc Schütz wrote: On Friday, 30 December 2016 at 13:45:23 UTC, Martin wrote: Are there any C-like bitfields in D? Yes - How can I use them? No - What could be used in their stead? Not built-in, but in the standard library: https://dlang.org/phobo

Re: DIP10005: Dependency-Carrying Declarations is now available for community feedback

2016-12-30 Thread deadalnix via Digitalmars-d
On Wednesday, 28 December 2016 at 23:14:48 UTC, Andrei Alexandrescu wrote: On 12/28/16 10:48 AM, deadalnix wrote: On Saturday, 24 December 2016 at 15:44:18 UTC, Andrei Alexandrescu wrote: A compiler enhancement can do this _without_ a language change. The language addition has additional bene

Re: DIP10005: Dependency-Carrying Declarations is now available for community feedback

2016-12-30 Thread Stefan Koch via Digitalmars-d
On Friday, 30 December 2016 at 18:11:54 UTC, deadalnix wrote: I think the performance gain we are looking at here is marginal, and I don't expect people to change their code to get a marginal benefit, so I suggest the performance aspect of the change to be simply left aside. Yes, imports are

Re: CTFE Status

2016-12-30 Thread Stefan Koch via Digitalmars-d
On Thursday, 29 December 2016 at 18:21:30 UTC, Stefan Koch wrote: Hi Guys, I just figured out why array constants did not work as function arguments. It's because the array-constant undergoes a cast when used as slice, while an array literal can be taken as is. The currently newCTFE does not

Re: const(Rvalue) resolved to different overloads

2016-12-30 Thread Ali Çehreli via Digitalmars-d
On 12/29/2016 11:59 PM, Jonathan M Davis via Digitalmars-d wrote: > In practice, I wouldn't expect it to matter - and usually if > you've overloaded on mutable and immutable, you're going to > want to overload on const as well anyway Coming up with such guidelines is exactly the reason why I was

Re: DIP10005: Dependency-Carrying Declarations is now available for community feedback

2016-12-30 Thread Chris Wright via Digitalmars-d
On Fri, 30 Dec 2016 18:18:12 +, Stefan Koch wrote: > I am still not sure what problem it is trying to solve :) * Performance improvements, primarily when a module imports another, bulky module for optional functionality. * Making it easier to locate where things are defined when reading code.

Re: DIP10005: Dependency-Carrying Declarations is now available for community feedback

2016-12-30 Thread Stefan Koch via Digitalmars-d
On Friday, 30 December 2016 at 22:29:18 UTC, Chris Wright wrote: * Performance improvements, primarily when a module imports another, bulky module for optional functionality. That is solved by selective imports. * Making it easier to locate where things are defined when reading code. That i

Re: DIP10005: Dependency-Carrying Declarations is now available for community feedback

2016-12-30 Thread Andrei Alexandrescu via Digitalmars-d
Stefan Koch wrote: > On Friday, 30 December 2016 at 22:29:18 UTC, Chris Wright wrote: >> * Performance improvements, primarily when a module imports >> another, >> bulky module for optional functionality. > That is solved by selective imports. > >> * Making it easier to locate where things are d

Re: DIP10005: Dependency-Carrying Declarations is now available for community feedback

2016-12-30 Thread ArturG via Digitalmars-d
On Friday, 30 December 2016 at 23:49:23 UTC, Andrei Alexandrescu wrote: The main win, which indeed is not emphasized enough, is better encapsulation. Walter pointed that out, and I will redo the DIP to put that front and center. Maybe i can provide an example where i think DCD's would be us

Re: DIP10005: Dependency-Carrying Declarations is now available for community feedback

2016-12-30 Thread Chris Wright via Digitalmars-d
On Fri, 30 Dec 2016 22:42:39 +, Stefan Koch wrote: > On Friday, 30 December 2016 at 22:29:18 UTC, Chris Wright wrote: >> * Performance improvements, primarily when a module imports another, >> bulky module for optional functionality. > That is solved by selective imports. Well, not today, but

Re: DIP10005: Dependency-Carrying Declarations is now available for community feedback

2016-12-30 Thread Chris Wright via Digitalmars-d
On Fri, 30 Dec 2016 23:49:23 +, Andrei Alexandrescu wrote: > The main win, which indeed is not emphasized enough, is better > encapsulation. Walter pointed that out, and I will redo the DIP to put > that front and center. Encapsulation is an abstraction over several concrete benefits. We're no

Re: DIP10005: Dependency-Carrying Declarations is now available for community feedback

2016-12-30 Thread Andrei Alexandrescu via Digitalmars-d
On 12/30/16 7:32 PM, Chris Wright wrote: On Fri, 30 Dec 2016 22:42:39 +, Stefan Koch wrote: On Friday, 30 December 2016 at 22:29:18 UTC, Chris Wright wrote: * Performance improvements, primarily when a module imports another, bulky module for optional functionality. That is solved by sele

Re: DIP10005: Dependency-Carrying Declarations is now available for community feedback

2016-12-30 Thread Andrei Alexandrescu via Digitalmars-d
On 12/30/16 7:34 PM, Chris Wright wrote: On Fri, 30 Dec 2016 23:49:23 +, Andrei Alexandrescu wrote: The main win, which indeed is not emphasized enough, is better encapsulation. Walter pointed that out, and I will redo the DIP to put that front and center. Encapsulation is an abstraction o

Re: DIP10005: Dependency-Carrying Declarations is now available for community feedback

2016-12-30 Thread Chris Wright via Digitalmars-d
On Fri, 30 Dec 2016 21:13:19 -0500, Andrei Alexandrescu wrote: > DIP1005 can't be in > the business of arguing that encapsulation is good by means of examples. Right. I said we should talk about the concrete benefits of the proposal instead of talking about encapsulation.