On Wednesday, 5 September 2018 at 01:39:04 UTC, Paul Backus wrote:
On Wednesday, 5 September 2018 at 00:49:36 UTC, Everlast wrote:
There is really no incentive for me to use D except for it's
language features... everything else it does, besides
performance, is shit compared to what most other
On Wednesday, 5 September 2018 at 05:44:38 UTC, H. S. Teoh wrote:
On Wed, Sep 05, 2018 at 01:18:17AM +, James Blachly via
Digitalmars-d wrote:
On Wednesday, 5 September 2018 at 00:49:36 UTC, Everlast wrote:
> I downloaded 3ddemo, extracted, built and I get these errors:
>
...
[...]
Are yo
On Wednesday, 5 September 2018 at 05:44:38 UTC, H. S. Teoh wrote:
To me, this strongly suggests the following idea:
- add *all* dlang.org packages to our current autotester / CI
infrastructure.
- if a particular (version of a) package builds successfully,
log the
compiler version / git hash
On Wednesday, 5 September 2018 at 04:32:18 UTC, SrMordred wrote:
Wouldn´t be interesting to specify the compiler version on
dub.json?
(I think ruby uses this idea)
Ruby 1.8 stuck around for four years before Ruby 1.9 came out.
Then it was six years until Ruby 2.0 came out. These days,
there'
On Wed, Sep 05, 2018 at 01:18:17AM +, James Blachly via Digitalmars-d wrote:
> On Wednesday, 5 September 2018 at 00:49:36 UTC, Everlast wrote:
> > I downloaded 3ddemo, extracted, built and I get these errors:
> >
> ...
[...]
> Are you talking about this?
>
> https://github.com/clinei/3ddemo
>
On Tue, 4 Sep 2018 at 21:40, Walter Bright via Digitalmars-d
wrote:
>
> On 9/4/2018 5:31 PM, Manu wrote:
> > I'm just showing one case that you tend to be confronted with
> > immediately, which is that if you import a module, and then open a
> > namespace with the same name as the root namespace o
On Tue, 4 Sep 2018 at 22:05, Joakim via Digitalmars-d
wrote:
>
> On Wednesday, 5 September 2018 at 01:20:26 UTC, Manu wrote:
> > On Tue, 4 Sep 2018 at 17:50, tide via Digitalmars-d
> > wrote:
> >>
> >> On Wednesday, 5 September 2018 at 00:35:50 UTC, Manu wrote:
> >> > On Tue, 4 Sep 2018 at 17:30,
On Tue, 4 Sep 2018 at 21:40, Walter Bright via Digitalmars-d
wrote:
>
> On 9/4/2018 5:31 PM, Manu wrote:
> > I'm just showing one case that you tend to be confronted with
> > immediately, which is that if you import a module, and then open a
> > namespace with the same name as the root namespace o
On Wednesday, 5 September 2018 at 04:39:14 UTC, Walter Bright
wrote:
On 9/4/2018 5:31 PM, Manu wrote:
I'm just showing one case that you tend to be confronted with
immediately, which is that if you import a module, and then
open a
namespace with the same name as the root namespace of a module
On Wednesday, 5 September 2018 at 01:20:26 UTC, Manu wrote:
On Tue, 4 Sep 2018 at 17:50, tide via Digitalmars-d
wrote:
On Wednesday, 5 September 2018 at 00:35:50 UTC, Manu wrote:
> On Tue, 4 Sep 2018 at 17:30, tide via Digitalmars-d
> wrote:
>> [...]
>
> And yes, the example is actually com
On 9/4/2018 5:31 PM, Manu wrote:
I'm just showing one case that you tend to be confronted with
immediately, which is that if you import a module, and then open a
namespace with the same name as the root namespace of a module you
imported, that is an error condition; the namespace conflicts with t
On Wednesday, 5 September 2018 at 01:58:50 UTC, Jonathan M Davis
wrote:
On Tuesday, September 4, 2018 7:18:17 PM MDT James Blachly via
Digitalmars-d wrote:
[...]
This is part of why it's sometimes been discussed that we need
a way to indicate which dub packages are currently maintained
and w
On Tuesday, September 4, 2018 8:37:16 PM MDT Dylan Graham via Digitalmars-d
wrote:
> On Wednesday, 5 September 2018 at 02:10:27 UTC, Jonathan M Davis
>
> wrote:
> > [...]
>
> Sure, yeah, but if you're using a package that hasn't been
> maintained in 2-3 years you need to take whether it will work
On Saturday, September 1, 2018 5:46:55 PM MDT Walter Bright via Digitalmars-
d wrote:
> On 9/1/2018 3:58 PM, Adam D. Ruppe wrote:
> > On Saturday, 1 September 2018 at 22:10:27 UTC, Nick Sabalausky wrote:
> >> I've used StackOverflow. It's NOT a place for asking and answering
> >> questions.>
> > I
On Wednesday, 5 September 2018 at 02:10:27 UTC, Jonathan M Davis
wrote:
[...]
Sure, yeah, but if you're using a package that hasn't been
maintained in 2-3 years you need to take whether it will work
with a grain of salt anyway.
On Tuesday, August 21, 2018 1:25:14 PM MDT Walter Bright via Digitalmars-d
wrote:
> On 8/21/2018 7:18 AM, Seb wrote:
> >> some rely on stackoverflow, some have an active wiki
> >
> > There are a few good points to move D.learn to Stack Overflow and that's
> > actually one thing that we have talked
On Tuesday, August 21, 2018 8:40:32 AM MDT Steven Schveighoffer via
Digitalmars-d wrote:
> On the contrary, many of the regular contributors here, don't give a
> lick about the forum software, as long as it's primarily backed by the
> newsgroup server. Many, including myself use the NG server, man
On Tuesday, September 4, 2018 7:54:49 PM MDT Dylan Graham via Digitalmars-d
wrote:
> On Wednesday, 5 September 2018 at 00:49:36 UTC, Everlast wrote:
> > I downloaded 3ddemo, extracted, built and I get these errors:
> >
> > logger 2.66.0: building configuration "library"...
> > \dub\packages\logger
On Tuesday, September 4, 2018 7:18:17 PM MDT James Blachly via Digitalmars-d
wrote:
> On Wednesday, 5 September 2018 at 00:49:36 UTC, Everlast wrote:
> > I downloaded 3ddemo, extracted, built and I get these errors:
> ...
>
> > This is typical with most of my trials with D... something is
> > alwa
On Wednesday, 5 September 2018 at 00:49:36 UTC, Everlast wrote:
I downloaded 3ddemo, extracted, built and I get these errors:
logger 2.66.0: building configuration "library"...
\dub\packages\logger-2.66.0\logger\std\historical\logger\core.d(1717,16):
Error: cannot implicitly convert expression
On Wednesday, 5 September 2018 at 00:49:36 UTC, Everlast wrote:
There is really no incentive for me to use D except for it's
language features... everything else it does, besides
performance, is shit compared to what most other languages do.
Really, D wins on very few metrics but the D fanboys
On Tue, 4 Sep 2018 at 17:50, tide via Digitalmars-d
wrote:
>
> On Wednesday, 5 September 2018 at 00:35:50 UTC, Manu wrote:
> > On Tue, 4 Sep 2018 at 17:30, tide via Digitalmars-d
> > wrote:
> >>
> >> On Tuesday, 4 September 2018 at 23:32:31 UTC, Walter Bright
> >> wrote:
> >> > On 9/4/2018 3:33 P
On Wednesday, 5 September 2018 at 00:49:36 UTC, Everlast wrote:
I downloaded 3ddemo, extracted, built and I get these errors:
...
This is typical with most of my trials with D... something is
always broken all the time and I'm expected to jump through a
bunch of hoops to get it to work. Fil
On Tuesday, 4 September 2018 at 16:36:20 UTC, Nick Treleaven
wrote:
My syntax for parameters that may get aliased to another
parameter is to write the parameter number that may escape it
in its scope attribute:
On Sunday, 2 September 2018 at 05:14:58 UTC, Chris M. wrote:
void betty(ref scope i
On Wednesday, 5 September 2018 at 00:35:50 UTC, Manu wrote:
On Tue, 4 Sep 2018 at 17:30, tide via Digitalmars-d
wrote:
On Tuesday, 4 September 2018 at 23:32:31 UTC, Walter Bright
wrote:
> On 9/4/2018 3:33 PM, Manu wrote:
>> file1.d
>> -
>> module bliz.ecs.component_access;
>> import
I downloaded 3ddemo, extracted, built and I get these errors:
logger 2.66.0: building configuration "library"...
\dub\packages\logger-2.66.0\logger\std\historical\logger\core.d(1717,16):
Error: cannot implicitly convert expression logger of type shared(Logger) to
std.historical.logger.core.Logg
On Friday, 24 August 2018 at 19:26:40 UTC, Walter Bright wrote:
On 8/24/2018 6:04 AM, Chris wrote:
For about a year I've had the feeling that D is moving too
fast and going nowhere at the same time. D has to slow down
and get stable. D is past the experimental stage. Too many
people use it for
On Tue, 4 Sep 2018 at 17:30, tide via Digitalmars-d
wrote:
>
> On Tuesday, 4 September 2018 at 23:32:31 UTC, Walter Bright wrote:
> > On 9/4/2018 3:33 PM, Manu wrote:
> >> file1.d
> >> -
> >> module bliz.ecs.component_access;
> >> import bliz.ecs.table;
> >> import bliz.ecs.types;
> >> ext
On Tue, 4 Sep 2018 at 16:35, Walter Bright via Digitalmars-d
wrote:
>
> On 9/4/2018 3:33 PM, Manu wrote:
> > file1.d
> > -
> > module bliz.ecs.component_access;
> > import bliz.ecs.table;
> > import bliz.ecs.types;
> > extern(C++, bliz):
> > // things...
> >
> > Error: project\ecs\include\
On Tuesday, 4 September 2018 at 23:32:31 UTC, Walter Bright wrote:
On 9/4/2018 3:33 PM, Manu wrote:
file1.d
-
module bliz.ecs.component_access;
import bliz.ecs.table;
import bliz.ecs.types;
extern(C++, bliz):
// things...
Error: project\ecs\include\d2\bliz\ecs\component_access.d(7):
Er
On 9/4/2018 3:33 PM, Manu wrote:
file1.d
-
module bliz.ecs.component_access;
import bliz.ecs.table;
import bliz.ecs.types;
extern(C++, bliz):
// things...
Error: project\ecs\include\d2\bliz\ecs\component_access.d(7): Error:
namespace `bliz.ecs.component_access.bliz` conflicts with import
On Tue, 4 Sep 2018 at 16:00, Neia Neutuladh via Digitalmars-d
wrote:
>
> On Tuesday, 4 September 2018 at 22:33:34 UTC, Manu wrote:
> > Error: project\ecs\include\d2\bliz\ecs\component_access.d(7):
> > Error: namespace `bliz.ecs.component_access.bliz` conflicts
> > with import `bliz.ecs.component_a
On 09/04/2018 06:35 PM, Walter Bright wrote:
Another example I read on HackerNews today:
"I recall that during their most recent s3 outage Amazon's status page
was green across the board, because somehow all the assets that were
supposed to be displayed when things went wrong were themselves h
On Tuesday, 4 September 2018 at 16:36:20 UTC, Nick Treleaven
wrote:
Rust's lifetime syntax is noisy - the scope name is repeated,
and why require a name if it's usually not given a meaningful
one (`a`)?
Rust is more limited semantically due to unique mutability, so
it may have different requi
On Tuesday, 4 September 2018 at 22:33:34 UTC, Manu wrote:
Error: project\ecs\include\d2\bliz\ecs\component_access.d(7):
Error: namespace `bliz.ecs.component_access.bliz` conflicts
with import `bliz.ecs.component_access.bliz` at
project\ecs\include\d2\bliz\ecs\component_access.d(3)
The obvious
Another example I read on HackerNews today:
"I recall that during their most recent s3 outage Amazon's status page was green
across the board, because somehow all the assets that were supposed to be
displayed when things went wrong were themselves hosted on the thing that was down."
https://n
On 09/04/2018 04:00 PM, Jonathan M Davis wrote:
On Tuesday, September 4, 2018 5:56:54 AM MDT ShadoLight via Digitalmars-d
wrote:
We work full-time for employers which, in my case, employs
thousands of engineers - and as a result engineering principles
are applied to everything - including tools.
On 9/3/2018 11:55 AM, Joakim wrote:
On Monday, 3 September 2018 at 16:55:10 UTC, Jonathan M Davis wrote:
But if you're ever expecting IDE support to be a top priority of many of the
contributors, then you're going to be sorely disappointed. It's the sort of
thing that we care about because we c
file1.d
-
module bliz.ecs.component_access;
import bliz.ecs.table;
import bliz.ecs.types;
extern(C++, bliz):
// things...
Error: project\ecs\include\d2\bliz\ecs\component_access.d(7): Error:
namespace `bliz.ecs.component_access.bliz` conflicts with import
`bliz.ecs.component_access.bliz` a
On Tuesday, 4 September 2018 at 21:36:16 UTC, Walter Bright wrote:
On 9/1/2018 4:12 AM, Chris wrote:
Hope is usually the last thing to die. But one has to be wise
enough to see that sometimes there is nothing one can do. As
things are now, for me personally D is no longer an option,
because of
https://issues.dlang.org/show_bug.cgi?id=19221
On 9/4/2018 12:59 PM, Timon Gehr wrote:
[...]
Thanks for the great explanation! Not sure I thoroughly understand it, though.
Therefore, D immutable/pure are both too strong and too weak: they prevent
@system code from implementing value representations that internally use
mutation (therefor
On 9/1/2018 4:12 AM, Chris wrote:
Hope is usually the last thing to die. But one has to be wise enough to see that
sometimes there is nothing one can do. As things are now, for me personally D is
no longer an option, because of simple basic things, like autodecode, a flaw
that will be there for
On Tuesday, 4 September 2018 at 20:45:53 UTC, H. S. Teoh wrote:
happens. Things aren't going to materialize out of thin air
just because people demand for it loudly enough, even if we'd
like for that to happen. *Somebody* has to do the work. That's
just how the universe works.
Human beings
On Tuesday, September 4, 2018 2:45:53 PM MDT H. S. Teoh via Digitalmars-d
wrote:
> Those who've learned LaTeX swear by it. Those who are learning LaTeX swear
> at it. -- Pete Bleackley
Well, that's a weirdly appropriate quote. The primary reason that I've done
as much with latex as I have is so t
On Tue, Sep 04, 2018 at 02:00:37PM -0600, Jonathan M Davis via Digitalmars-d
wrote:
[...]
> And while a number of us do do at least some work on D-related stuff
> that we don't care about aside from wanting to improve the D ecosystem
> for others, when the vast majority of the time being put in is
On Tuesday, September 4, 2018 5:56:54 AM MDT ShadoLight via Digitalmars-d
wrote:
> We work full-time for employers which, in my case, employs
> thousands of engineers - and as a result engineering principles
> are applied to everything - including tools. So all SW dev teams
> here use standardized
On 29.08.2018 22:01, Walter Bright wrote:
On 8/29/2018 10:50 AM, Timon Gehr wrote:
D const/immutable is stronger than immutability in Haskell (which is
usually _lazy_).
I know Haskell is lazy, but don't see the connection with a weaker
immutability guarantee.
In D, you can't have a lazy val
On 02.09.2018 15:45, bauss wrote:
On Sunday, 2 September 2018 at 13:26:55 UTC, Petar Kirov [ZombineDev]
wrote:
It's intended, but with the possibility to add special syntax for
local declarations in the future left open, as per:
https://github.com/dlang/DIPs/blob/master/DIPs/accepted/DIP1010.md#
On Tuesday, 4 September 2018 at 03:39:04 UTC, Nick Sabalausky
(Abscissa) wrote:
It seems pretty well established around here that:
1. Doing anything after a process has entered an unknown state
is dangerous, and the more activity, the more danger (Note
also, the transition to an unknown state
On Mon, Sep 03, 2018 at 11:39:04PM -0400, Nick Sabalausky (Abscissa) via
Digitalmars-d wrote:
> It seems pretty well established around here that:
>
> 1. Doing anything after a process has entered an unknown state is
> dangerous, and the more activity, the more danger [...]
>
> 2. For practical
On Tuesday, 4 September 2018 at 13:34:03 UTC,
TheSixMillionDollarMan wrote:
I think D's 'core' problem, is that it's trying to compete
with, what are now, widely used, powerful, and well supported
languages, with sophisticate ecosystems in place already.
C/C++/Java/C# .. just for beginners.
Y
On Friday, 24 August 2018 at 13:21:25 UTC, Jonathan M Davis wrote:
On Friday, August 24, 2018 6:05:40 AM MDT Mike Franklin via
Digitalmars-d wrote:
> You're basically trying to bypass the OS' public API if
> you're trying to bypass libc.
No I'm trying to bypass libc and use the OS API directly
The "Install .exe" on the main page looks sloppy to me. My brain
wants to read it as "Install.exe" and wonders why there's a space
before the dot. What the author actually meant is probably
"Installation executable".
That's "The Button" on the main D page, so I suggest we use a
better title.
On Tue, 04 Sep 2018 11:56:54 +, ShadoLight wrote:
> I know the "we use Vim/Emacs, why don't you pitch in and help on VisualD
> if you want to use it" view is valid opinion, but it will not bring the
> masses since it will never happen - the critical mass is composed of
> devs that want to _use
On Monday, 3 September 2018 at 02:58:01 UTC, Nick Sabalausky
(Abscissa) wrote:
In the 50's/60's in particular, I imagine a much larger
percentage of programmers probably had either some formal
engineering background or something equally strong.
I guess some had, but my impression it that it wa
Rust's lifetime syntax is noisy - the scope name is repeated, and
why require a name if it's usually not given a meaningful one
(`a`)?
Rust is more limited semantically due to unique mutability, so it
may have different requirements for function signatures to D. (I
think they recently tweaked
The first search engines were created in 1993, google came
along in 1998 after at least two dozen others in that list, and
didn't make a profit till 2001. Some of those early competitors
were giant "billion dollar global companies," yet it's google
that dominates the web search engine market to
On Tuesday, 4 September 2018 at 14:23:33 UTC, Joakim wrote:
The first search engines were created in 1993, google came
along in 1998 after at least two dozen others in that list, and
didn't make a profit till 2001. Some of those early competitors
were giant "billion dollar global companies," ye
On Tuesday, 4 September 2018 at 11:21:24 UTC, Kagamin wrote:
On Sunday, 2 September 2018 at 21:07:20 UTC, Nick Sabalausky
(Abscissa) wrote:
B. Physical interface:
--
By this I mean both actual input devices (keyboards,
controllers, pointing devices) and also the mappings fr
On Tuesday, 4 September 2018 at 13:34:03 UTC,
TheSixMillionDollarMan wrote:
On Tuesday, 4 September 2018 at 01:36:53 UTC, Mike Parker wrote:
On Monday, 3 September 2018 at 18:26:57 UTC, Chris wrote:
And of course, low manpower and funding aren't the complete
picture. Management also play a rol
On Tuesday, 4 September 2018 at 01:36:53 UTC, Mike Parker wrote:
On Monday, 3 September 2018 at 18:26:57 UTC, Chris wrote:
And of course, low manpower and funding aren't the complete
picture. Management also play a role. Both Walter and Andrei
have freely admitted they are not managers and tha
On 04/09/2018 11:47 PM, Kagamin wrote:
On Tuesday, 4 September 2018 at 06:32:02 UTC, rikki cattermole wrote:
If D didn't have built-in OOP features already, it'd be an
interesting question, but given that it does, I think getting rid of
them is a clear net-negative.
You also loose loads of st
On Tuesday, 4 September 2018 at 00:16:16 UTC, Nick Sabalausky
(Abscissa) wrote:
On 09/03/2018 02:55 PM, Joakim wrote:
On Monday, 3 September 2018 at 16:55:10 UTC, Jonathan M Davis
wrote:
But if you're ever expecting IDE support to be a top priority
of many of the contributors, then you're going
On Tuesday, 4 September 2018 at 06:32:02 UTC, rikki cattermole
wrote:
If D didn't have built-in OOP features already, it'd be an
interesting question, but given that it does, I think getting
rid of them is a clear net-negative.
You also loose loads of stuff like extern(C++) classes interop
an
On Sunday, 2 September 2018 at 21:07:20 UTC, Nick Sabalausky
(Abscissa) wrote:
B. Physical interface:
--
By this I mean both actual input devices (keyboards,
controllers, pointing devices) and also the mappings from their
affordances (ie, what you can do with them: push but
On Sunday, 2 September 2018 at 21:07:20 UTC, Nick Sabalausky
(Abscissa) wrote:
GUI programming has been attempted a lot. (See Scratch for one
of the latest, possibly most successful attempts). But there
are real, practical reasons it's never made significant
in-roads (yet).
There are really t
On 04/09/2018 10:27 PM, Ecstatic Coder wrote:
On Tuesday, 4 September 2018 at 09:56:13 UTC, rikki cattermole wrote:
On 04/09/2018 9:40 PM, Ecstatic Coder wrote:
But it seems that the latest version of "std.file.copy" now
completely ignores the "PreserveAttributes.no" argument on Windows,
which
On Tuesday, 4 September 2018 at 09:56:13 UTC, rikki cattermole
wrote:
On 04/09/2018 9:40 PM, Ecstatic Coder wrote:
But it seems that the latest version of "std.file.copy" now
completely ignores the "PreserveAttributes.no" argument on
Windows, which made recent Windows builds of Resync fail on
On Tuesday, 4 September 2018 at 09:40:23 UTC, Ecstatic Coder
wrote:
But it seems that the latest version of "std.file.copy" now
completely ignores the "PreserveAttributes.no" argument on
Windows, which made recent Windows builds of Resync fail on
read-only files.
Very typical...
While D rema
On Thursday, 23 August 2018 at 06:34:01 UTC, nkm1 wrote:
On Thursday, 23 August 2018 at 05:37:12 UTC, Shachar Shemesh
wrote:
Let's start with this one:
https://issues.dlang.org/show_bug.cgi?id=14246#c6
The problems I'm talking about are not easily fixable. They
stem from features not playing w
On 04/09/2018 9:40 PM, Ecstatic Coder wrote:
But it seems that the latest version of "std.file.copy" now completely
ignores the "PreserveAttributes.no" argument on Windows, which made
recent Windows builds of Resync fail on read-only files.
What???
There is nothing in the changelog between 2.
On Thursday, 23 August 2018 at 03:50:44 UTC, Shachar Shemesh
wrote:
On 22/08/18 21:34, Ali wrote:
On Wednesday, 22 August 2018 at 17:42:56 UTC, Joakim wrote:
Pretty positive overall, and the negatives he mentions are
fairly obvious to anyone paying attention.
Yea, I agree, the negatives are n
On Tuesday, 4 September 2018 at 05:38:49 UTC, Iain Buclaw wrote:
On 4 September 2018 at 04:19, Laeeth Isharc via Digitalmars-d
wrote:
On Monday, 3 September 2018 at 16:07:21 UTC, RhyS wrote:
A good example being the resources going into DMD, LDC,
GDC... 3 Compilers for one language, when eve
On Monday, 3 September 2018 at 16:41:32 UTC, Iain Buclaw wrote:
15 years ago, people were complaining that there was only one D
compiler. It is ironic that people now complain that there's
too many.
One needs multiple implementations to confirm the accuracy of the
language specification. D s
On Tuesday, 4 September 2018 at 01:36:53 UTC, Mike Parker wrote:
On Monday, 3 September 2018 at 18:26:57 UTC, Chris wrote:
I think this sort of misunderstanding is the source of a lot
of friction on this forum. Some users think (or in my case:
thought) that D will be a sound and stable langu
On Tuesday, 4 September 2018 at 01:36:53 UTC, Mike Parker wrote:
D is not a petri dish for testing ideas. It's not an experiment.
Well, the general consensus for programming languages is that it
a language is experimental
(or proprietary) until it is fully specced out as a stable
formal stan
77 matches
Mail list logo
