On Friday, 9 February 2018 at 15:46:56 UTC, Mike Parker wrote:
On Friday, 9 February 2018 at 15:37:12 UTC, Ralph Doncaster
wrote:
I think you are proving my point. You say there is no
difference between:
const MAX_IN = 20;
vs
immutable MAX_IN = 20;
So now I have to try both, and look at
On Fri, 2018-02-09 at 14:04 +, rumbu via Digitalmars-d wrote:
>
[…]
> 1. Keeps data in the %APPDATA%/Roaming folder. Connecting my
> computer to the company network means that AD will sync zillions
> of files on the company profile server. This issue is 4 years
> old:
On Fri, 2018-02-09 at 13:51 +, Atila Neves via Digitalmars-d wrote:
> On Friday, 9 February 2018 at 13:34:01 UTC, tetyys wrote:
> > On Friday, 9 February 2018 at 13:10:16 UTC, rumbu wrote:
> > >
> > > And not a language feature but I hate dub. Just saying.
> >
> > Why do people hate dub? I
On Friday, 9 February 2018 at 15:37:12 UTC, Ralph Doncaster wrote:
I think you are proving my point. You say there is no
difference between:
const MAX_IN = 20;
vs
immutable MAX_IN = 20;
So now I have to try both, and look at the generated code to be
sure.
Or read the docs:
On Friday, 9 February 2018 at 15:35:38 UTC, Mike Parker wrote:
On Friday, 9 February 2018 at 15:27:18 UTC, Andrea Fontana
wrote:
If you need to take the address of a constant, use immutable
or const (doesn't really matter, but I prefer immutable). If
you don't need the address, use enum.
On Friday, 9 February 2018 at 15:09:10 UTC, Mike Parker wrote:
On Friday, 9 February 2018 at 14:59:38 UTC, Ralph Doncaster
wrote:
const auto MAX_IN = 20;
const MAX_IN = 20;
The auto is superfluous and is only needed when there's no
storage class or type.
Others say to use enums. It
On Friday, 9 February 2018 at 15:29:52 UTC, Ralph Doncaster wrote:
My point is that in D, the docs say "private" will keep the
definition out of the object file. I think you'll have to
agree that it's at least confusing.
The exact quote is: "Static does not have the additional C
meaning of
On Friday, 9 February 2018 at 15:27:18 UTC, Andrea Fontana wrote:
If you need to take the address of a constant, use immutable
or const (doesn't really matter, but I prefer immutable). If
you don't need the address, use enum.
Why not static immutable?
For global scope? static has no effect
On Friday, 9 February 2018 at 15:09:10 UTC, Mike Parker wrote:
On Friday, 9 February 2018 at 14:59:38 UTC, Ralph Doncaster
wrote:
const auto MAX_IN = 20;
const MAX_IN = 20;
The auto is superfluous and is only needed when there's no
storage class or type.
Others say to use enums. It
On Friday, 9 February 2018 at 15:05:05 UTC, Jonathan M Davis
wrote:
[...]
The reality of the matter is that shared is _supposed_ to
result in a bunch of compilation errors when you try to do
stuff to it. You're supposed to either use atomics to mutate a
shared object or protect it with a
On Friday, 9 February 2018 at 15:05:05 UTC, Jonathan M Davis
wrote:
The memory model needs to be properly defined like C++ finally
did. It works without that, but as I understand it, it's
technically relying too much on implementation-defined behavior.
[snip]
Thanks for the write-up!
On Friday, 9 February 2018 at 15:03:02 UTC, Adam D. Ruppe wrote:
On Friday, 9 February 2018 at 14:59:38 UTC, Ralph Doncaster
wrote:
The docs say using "private" will keep the symbol out of the
file, but that is not true.
https://dlang.org/spec/attribute.html#static
That sentence isn't well
On Friday, 9 February 2018 at 13:47:51 UTC, Atila Neves wrote:
On Friday, 9 February 2018 at 08:27:21 UTC, Nick Sabalausky
And yes, things like "inout", "auto ref" or whatever, and
such, strike me as indicative of more fundamental design
flaws. (Not "flaw" in the sence of "mistakes"
On Friday, 9 February 2018 at 13:53:51 UTC, Seb wrote:
On Friday, 9 February 2018 at 13:10:16 UTC, rumbu wrote:
On Friday, 9 February 2018 at 08:27:21 UTC, Nick Sabalausky
(Abscissa) wrote:
Defining input ranges (one of my biggest pet peeves):
C# knocked it out of the park ages ago with its
On Friday, 9 February 2018 at 14:59:38 UTC, Ralph Doncaster wrote:
const auto MAX_IN = 20;
const MAX_IN = 20;
The auto is superfluous and is only needed when there's no
storage class or type.
Others say to use enums. It turns out enums seems to be the
best, as they don't create a
On Friday, February 09, 2018 14:48:36 jmh530 via Digitalmars-d wrote:
> On Friday, 9 February 2018 at 14:01:23 UTC, Andrea Fontana wrote:
> > [snip]
> > - Unfinished parts of language (ex: shared?)
>
> I see this a lot, but I don't really use shared so I always
> forget how exactly it is
On Friday, 9 February 2018 at 14:59:38 UTC, Ralph Doncaster wrote:
The docs say using "private" will keep the symbol out of the
file, but that is not true.
https://dlang.org/spec/attribute.html#static
That sentence isn't well written since D's private and C's static
are different... what
On Friday, 9 February 2018 at 07:54:49 UTC, Suliman wrote:
Which language futures by your opinion make D harder?
Too many choices. I tend to obsess over the best way to do
something, and when the language gives me several options I want
to try them all. One example is constants (that would
On Friday, 9 February 2018 at 14:01:23 UTC, Andrea Fontana wrote:
[snip]
- Unfinished parts of language (ex: shared?)
I see this a lot, but I don't really use shared so I always
forget how exactly it is unfinished. If there are unfinished
parts of the language, it couldn't hurt to put in
On Friday, 9 February 2018 at 07:54:49 UTC, Suliman wrote:
I like D, but sometimes it's look like for me too complicated.
Go have a lot of fans even it not simple, but primitive. But
some D futures make it very hard to learning.
Small list by me:
1. mixins
2. inout
3. too many attributes
On Friday, 9 February 2018 at 07:54:49 UTC, Suliman wrote:
Which language futures by your opinion make D harder?
shared.
On Friday, 9 February 2018 at 13:34:01 UTC, tetyys wrote:
On Friday, 9 February 2018 at 13:10:16 UTC, rumbu wrote:
And not a language feature but I hate dub. Just saying.
Why do people hate dub? I think it's a great package manager
and build tool
1. Keeps data in the %APPDATA%/Roaming
On Friday, 9 February 2018 at 07:54:49 UTC, Suliman wrote:
I like D, but sometimes it's look like for me too complicated.
Go have a lot of fans even it not simple, but primitive. But
some D futures make it very hard to learning.
Small list by me:
1. mixins
2. inout
3. too many attributes
On Friday, 9 February 2018 at 13:34:01 UTC, tetyys wrote:
On Friday, 9 February 2018 at 13:10:16 UTC, rumbu wrote:
And not a language feature but I hate dub. Just saying.
Why do people hate dub? I think it's a great package manager
and build tool
Great package manager? Yes.
Great build
On Friday, 9 February 2018 at 13:10:16 UTC, rumbu wrote:
On Friday, 9 February 2018 at 08:27:21 UTC, Nick Sabalausky
(Abscissa) wrote:
[...]
I'm missing too the yield return and await syntax in D every
time. In my current asp.net project I counted around 800 await
calls. I don't even
On Friday, 9 February 2018 at 13:10:16 UTC, rumbu wrote:
On Friday, 9 February 2018 at 08:27:21 UTC, Nick Sabalausky
(Abscissa) wrote:
Defining input ranges (one of my biggest pet peeves):
C# knocked it out of the park ages ago with its design for a
stackless!!! (ie no-fibers) coroutine
On Friday, February 09, 2018 13:34:01 tetyys via Digitalmars-d wrote:
> On Friday, 9 February 2018 at 13:10:16 UTC, rumbu wrote:
> > And not a language feature but I hate dub. Just saying.
>
> Why do people hate dub? I think it's a great package manager and
> build tool
I don't know what all of
On Friday, 9 February 2018 at 08:27:21 UTC, Nick Sabalausky
(Abscissa) wrote:
On 02/09/2018 02:54 AM, Suliman wrote:
[...]
And yes, things like "inout", "auto ref" or whatever, and such,
strike me as indicative of more fundamental design flaws. (Not
"flaw" in the sence of "mistakes"
On Friday, 9 February 2018 at 13:10:16 UTC, rumbu wrote:
And not a language feature but I hate dub. Just saying.
Why do people hate dub? I think it's a great package manager and
build tool
On Friday, 9 February 2018 at 08:27:21 UTC, Nick Sabalausky
(Abscissa) wrote:
Defining input ranges (one of my biggest pet peeves):
C# knocked it out of the park ages ago with its design for a
stackless!!! (ie no-fibers) coroutine syntax. There's no reason
the same approach couldn't be used
On Friday, 9 February 2018 at 07:54:49 UTC, Suliman wrote:
I like D, but sometimes it's look like for me too complicated.
Go have a lot of fans even it not simple, but primitive. But
some D futures make it very hard to learning.
Small list by me:
1. mixins
2. inout
3. too many attributes
On 02/09/2018 02:54 AM, Suliman wrote:
I like D, but sometimes it's look like for me too complicated. Go have a
lot of fans even it not simple, but primitive. But some D futures make
it very hard to learning.
Small list by me:
1. mixins
2. inout
3. too many attributes like: @safe @system
101 - 132 of 132 matches
Mail list logo
