On 24/08/2018 1:22 AM, Shachar Shemesh wrote:
Except what I'd _really_ like to do is for them to be the same thing.
I'd like inheritance. Except I can't do that for structs, and if I
defined SockAddr as a class, I'd mandate allocating it on the GC,
violating the whole point behind writing
On Thu, Aug 23, 2018 at 09:51:43PM +1200, rikki cattermole via Digitalmars-d
wrote:
> On 23/08/2018 9:45 PM, Mihails wrote:
> > On Thursday, 23 August 2018 at 09:30:45 UTC, rikki cattermole wrote:
> > > Whoever acts as a project manager would need to be given the
> > > ability to override W as
On Thursday, 23 August 2018 at 07:37:07 UTC, Iain Buclaw wrote:
On Thursday, 23 August 2018 at 06:58:13 UTC, Joakim wrote:
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
On Thursday, 23 August 2018 at 15:14:07 UTC, Steven Schveighoffer
wrote:
On 8/23/18 9:32 AM, Steven Schveighoffer wrote:
[...]
Actually, thinking about this, the shortest lifetime is
dictated by how it is called, so there is no valid way to
determine which one makes sense when compiling the
On Thursday, 23 August 2018 at 09:26:46 UTC, rikki cattermole
wrote:
On 23/08/2018 9:09 PM, Shachar Shemesh wrote:
functions may be @safe, nothrow, @nogc, pure. If it's a method
it might also be const/inout/immutable, static. The number of
libraries that support all combinations is exactly
On 8/23/18 4:58 AM, Walter Bright wrote:
On 8/22/2018 6:50 AM, Steven Schveighoffer wrote:
What about:
size_t put(sink, parameters...)
Does this qualify as the sink being the "return" type? Obviously the
real return can't contain any references, so it trivially can be ruled
out as the
On Thursday, 23 August 2018 at 13:22:45 UTC, Shachar Shemesh
wrote:
Because in D, structs can't inherit,
Forgive me if I'm not helping, but if you are willing to create a
little infrastructure, I think you can create polymorphic structs
with the technique described at
On Thursday, 23 August 2018 at 03:50:44 UTC, Shachar Shemesh
wrote:
To sum it up: fatal flaws + no path to fixing + no push from
the community = inevitable eventual death.
With great regrets,
Shachar
I want to jump in for the sake of someone from the outside coming
in and reading this to
On 8/22/18 11:37 AM, Alex wrote:
On Wednesday, 22 August 2018 at 15:18:29 UTC, XavierAP wrote:
On Wednesday, 22 August 2018 at 14:48:57 UTC, Alex wrote:
Because it could be meant as the argument to some templates to the
left. Like
(foo!bar)!x
Sure, it would be a coincidence, if both will
On Thursday, 23 August 2018 at 06:34:01 UTC, nkm1 wrote:
The only real problem with D is that it's a language designed
with
GC in mind, yet there are numerous attempts to use it without
GC.
Also, supporting GC-less programming gets in the way of
improving
D's GC (which is pretty damn bad by
On Thursday, 23 August 2018 at 09:09:40 UTC, Shachar Shemesh
wrote:
On 23/08/18 09:58, Joakim wrote:
Because you've not listed any here, which makes you no better
than some noob
Here's one: the forum does not respond well to criticism.
Well, I'm D hobbyist and of course it's not a perfect
On 8/23/18 9:22 AM, Shachar Shemesh wrote:
On the other hand, look at ConnectedSocket.connect:
https://weka-io.github.io/mecca/docs/mecca/reactor/io/fd/ConnectedSocket.connect.html
Why do I need two forms? What good is that? Why is the second form a
template? Answer: Because in D, structs
On Thursday, August 23, 2018 9:03:24 AM MDT Ali via Digitalmars-d wrote:
> RAII is nowadays described as C++ nicest , more important and
> most powerful feature
> D again, missed the opportunity on that one
D was designed to have RAII, and it does. It's just that the implementation
is buggy
https://issues.dlang.org/show_bug.cgi?id=18672
--- Comment #5 from RazvanN ---
PR : https://github.com/dlang/dmd/pull/8607
--
On Thu, Aug 23, 2018 at 06:39:32PM +0200, ag0aep6g via Digitalmars-d wrote:
> On 08/23/2018 05:17 PM, H. S. Teoh wrote:
> > And the nice thing about D being open source is that should the
> > situation escalate to the point where the community simply cannot
> > get along with W anymore, forking is
On Thursday, 23 August 2018 at 17:19:41 UTC, Ali wrote:
On Thursday, 23 August 2018 at 16:22:54 UTC, Shachar Shemesh
wrote:
On 23/08/18 17:01, Steven Schveighoffer wrote:
My main job is to develop for Weka, not develop D itself.
Weka, at some point, made the strategic decision to use a non
On 23/08/18 20:52, bachmeier wrote:
On Thursday, 23 August 2018 at 17:19:41 UTC, Ali wrote:
On Thursday, 23 August 2018 at 16:22:54 UTC, Shachar Shemesh wrote:
On 23/08/18 17:01, Steven Schveighoffer wrote:
My main job is to develop for Weka, not develop D itself.
Weka, at some point, made
On Thursday, 23 August 2018 at 17:52:54 UTC, bachmeier wrote:
On Thursday, 23 August 2018 at 17:19:41 UTC, Ali wrote:
On Thursday, 23 August 2018 at 16:22:54 UTC, Shachar Shemesh
wrote:
On 23/08/18 17:01, Steven Schveighoffer wrote:
My main job is to develop for Weka, not develop D itself.
On Thu, Aug 23, 2018 at 09:05:53PM +0300, Shachar Shemesh via Digitalmars-d
wrote:
> On 23/08/18 20:57, bachmeier wrote:
> > On Thursday, 23 August 2018 at 17:02:12 UTC, Shachar Shemesh wrote:
> >
> > > If you can, feel free to contact me off-list, and I'm fairly sure
> > > we can get the budget
On Thursday, 23 August 2018 at 09:51:43 UTC, rikki cattermole
wrote:
Good luck getting W to agree to it, especially when there is
yet another "critical D opportunity" on the table ;)
No. They have power for as long as we the community say that
they do.
We are at the point where they need a
On 8/23/18 12:27 PM, Shachar Shemesh wrote:
On 23/08/18 17:01, Steven Schveighoffer wrote:
So interestingly, you are accepting the sockaddr by VALUE.
Indeed. The reason is that I cannot accept them by reference, as then
you wouldn't be able to pass lvalues* in. Another controversial decision
On 24/08/2018 4:39 AM, ag0aep6g wrote:
Currently, I'm toying with ideas for a hobby language of my own. I know
that it most likely won't go anywhere, but wasting time on that starts
to feel more rewarding than wasting it on D.
I've been doing that for a few years now.
My parser generator is
On 23/08/18 18:35, Joakim wrote:
So your example of a fatal flaw is that D could be 100X faster at
compilation instead of just 10X than most every other native language
out there?! C'mon.
Have you tried Stephan's example yet?
static foreach(i; 0..16384) {}
Do give it a shot, tell me
On Thursday, 23 August 2018 at 17:19:41 UTC, Ali wrote:
On Thursday, 23 August 2018 at 16:22:54 UTC, Shachar Shemesh
wrote:
On 23/08/18 17:01, Steven Schveighoffer wrote:
My main job is to develop for Weka, not develop D itself.
Weka, at some point, made the strategic decision to use a non
On Thursday, 23 August 2018 at 18:05:53 UTC, Shachar Shemesh
wrote:
On 23/08/18 20:57, bachmeier wrote:
On Thursday, 23 August 2018 at 17:02:12 UTC, Shachar Shemesh
wrote:
If you can, feel free to contact me off-list, and I'm fairly
sure we can get the budget for you to work on it. The same
On Thursday, 23 August 2018 at 16:22:54 UTC, Shachar Shemesh
wrote:
On 23/08/18 17:01, Steven Schveighoffer wrote:
My main job is to develop for Weka, not develop D itself.
Weka, at some point, made the strategic decision to use a non
mainstream language
I dont think Weka, have a choice,
On 23/08/18 20:57, bachmeier wrote:
On Thursday, 23 August 2018 at 17:02:12 UTC, Shachar Shemesh wrote:
If you can, feel free to contact me off-list, and I'm fairly sure we
can get the budget for you to work on it. The same goes for anyone
else on this list.
I don't think Kenji will see
On Thursday, August 23, 2018 12:05:53 PM MDT Shachar Shemesh via
Digitalmars-d wrote:
> On 23/08/18 20:57, bachmeier wrote:
> > On Thursday, 23 August 2018 at 17:02:12 UTC, Shachar Shemesh wrote:
> >> If you can, feel free to contact me off-list, and I'm fairly sure we
> >> can get the budget for
On 8/23/18 12:22 PM, Shachar Shemesh wrote:
On 23/08/18 17:01, Steven Schveighoffer wrote:
I'm not saying all bugs you file will be fixed, but all bugs you
*don't* file will definitely not be fixed.
So far, my experience is that it has about the same chances of being
fixed both ways, and not
On Thursday, 23 August 2018 at 18:27:27 UTC, Abdulhaq wrote:
On Thursday, 23 August 2018 at 09:51:43 UTC, rikki cattermole
wrote:
Good luck getting W to agree to it, especially when there
is yet another "critical D opportunity" on the table ;)
No. They have power for as long as we the
On 23/08/18 17:01, Steven Schveighoffer wrote:
So interestingly, you are accepting the sockaddr by VALUE.
Indeed. The reason is that I cannot accept them by reference, as then
you wouldn't be able to pass lvalues in. Another controversial decision
by D.
Had that been C++, I'd definitely
On Thursday, 23 August 2018 at 16:22:54 UTC, Shachar Shemesh
wrote:
Waiting for the community to fix a bug in D that is blocking
Weka will get Weka kicked out of the market. There is no value
proposition. We simply have to work faster than that.
Oh, and our code base over 300,000 lines. Don't
On 23/08/18 17:01, Steven Schveighoffer wrote:
If they are blocking
your work, complain about them loudly, every day. But not filing them
doesn't help anyone.
The economics don't add up.
If a bug is blocking my work, there are two options:
1. I work around it, at which point it is no longer
On 08/23/2018 05:17 PM, H. S. Teoh wrote:
And the nice thing about D being open source is that should the
situation escalate to the point where the community simply cannot get
along with W anymore, forking is always an option.
But forking only happens when the dissenters have enough motivation
On Thursday, 23 August 2018 at 17:02:12 UTC, Shachar Shemesh
wrote:
On 23/08/18 18:35, Joakim wrote:
So your example of a fatal flaw is that D could be 100X faster
at compilation instead of just 10X than most every other
native language out there?! C'mon.
Have you tried Stephan's example
On Thursday, 23 August 2018 at 17:02:12 UTC, Shachar Shemesh
wrote:
If you can, feel free to contact me off-list, and I'm fairly
sure we can get the budget for you to work on it. The same goes
for anyone else on this list.
I don't think Kenji will see your message, but he may be able to
On 23/08/18 19:58, RhyS wrote:
A quick question, if Weka did not have the current 300k backlog of code,
what language of choice is more likely to be picked by the team at Weka?
I don't know. Like I said, while the feeling that D has completely lost
its way is fairly universal, the claim
On Wed, 2018-08-22 at 12:00 -0700, H. S. Teoh via Digitalmars-d wrote:
[…]
>
> I approached the article from a language-independent viewpoint. While
> I
> know a little bit of Python, I wasn't really very interested in the
> Python-specific aspects of the article, nor in the specific
>
On Thursday, 23 August 2018 at 12:03:59 UTC, Walter Bright wrote:
I'd appreciate a list of bugzilla issues you regard as critical
to your operations.
Sorry to weasle in, but
https://issues.dlang.org/show_bug.cgi?id=2043
Sorry for childish behaviour in bugzilla (my last comment), but
this bug
On 8/23/18 9:32 AM, Steven Schveighoffer wrote:
On 8/23/18 4:58 AM, Walter Bright wrote:
On 8/22/2018 6:50 AM, Steven Schveighoffer wrote:
As for things being made "more flexible in the future" this basically
translates to code breakage. For example, if you are depending on
only the first
On Friday, 24 August 2018 at 00:32:59 UTC, Guillaume Piolat wrote:
For example: why implement AVX in DMD backend? Who are the
users that will be delighted by that? Those interested in
performance already use some other back-end, it's imo a
completely useless development since _no one_ use
On Friday, 24 August 2018 at 00:13:48 UTC, Mike Franklin wrote:
On Thursday, 23 August 2018 at 23:36:07 UTC, Chris M. wrote:
Heck, now that I'm looking at it, DIP25 seems like a more
restricted form of Rust's lifetimes. Let me know if I'm just
completely wrong about this, but
I think DIP 25
On Friday, 24 August 2018 at 00:56:10 UTC, Mike Franklin wrote:
On Friday, 24 August 2018 at 00:53:20 UTC, Guillaume Piolat
wrote:
Do you also mean to reimplement everything related to FILE*?
floating-point parsing and conversion to string?
multithreaded malloc?
Only what's need for
On Friday, 24 August 2018 at 00:53:20 UTC, Guillaume Piolat wrote:
Do you also mean to reimplement everything related to FILE*?
floating-point parsing and conversion to string?
multithreaded malloc?
Only what's need for druntime. That would include multi-threaded
malloc, but not the FILE*
On 8/21/2018 2:41 PM, tide wrote:
What about if you accidentially press a button that posts the comment?
That's really up to your NNTP client's design, which we didn't implement. There
are lots of NNTP clients to choose from.
Why can't syntax formatting be implemented, does anyone disagree
On Thursday, August 23, 2018 3:31:41 PM MDT Walter Bright via Digitalmars-d
wrote:
> On 8/23/2018 9:19 AM, Jonathan M Davis wrote:
> > D was designed to have RAII, and it does. It's just that the
> > implementation is buggy (which is obviously a serious problem), so
> > depending on what your
On 24/08/2018 6:27 AM, Abdulhaq wrote:
On Thursday, 23 August 2018 at 09:51:43 UTC, rikki cattermole wrote:
Good luck getting W to agree to it, especially when there is yet
another "critical D opportunity" on the table ;)
No. They have power for as long as we the community say that they do.
On Wednesday, 22 August 2018 at 08:33:36 UTC, Andrey wrote:
Hello,
I know that D has build-in unit tests. If so, what mechanism D
provides for mocking objects?
I'd like to pose the question, what are you testing. This looks
like you are testing that your mocked object returns 10. I
usually
On 08/23/2018 07:28 PM, H. S. Teoh wrote:
On Thu, Aug 23, 2018 at 06:39:32PM +0200, ag0aep6g via Digitalmars-d wrote:
[...]
Regressions aren't being fixed (78 open). Wrong-code don't get fixed
(170!). Etc., and so on. So why even bother?
I think this is unfair. Regressions *are* being
On 23/08/18 23:46, Walter Bright wrote:
In my experience with debugging code, if drilling down to find the cause
of the problem is not done, there is no way to conclude whether whether
it is a compiler bug or a user bug.
(Of course, compiler internal errors are always compiler bugs.)
On 24/08/2018 1:57 PM, Shachar Shemesh wrote:
Consider the following line from the weka code base:
_trustedData.opIndex(diskIdx) &= NotBitmap(toDistrust);
That's strange. Why didn't Shachar just do?
_trustedData[diskIdx] &= NotBitmap(toDistrust);
Answer: Because the
https://issues.dlang.org/show_bug.cgi?id=19084
Jonathan Marler changed:
What|Removed |Added
CC||johnnymar...@gmail.com
--- Comment #1
On Friday, 24 August 2018 at 00:46:14 UTC, Mike Franklin wrote:
But I need it to implement `memcpy` and `memcmp` in D, so we
can remove the dependency on the D standard library :-)
Gah! What a typo. I mean the C standard library.
On Friday, 24 August 2018 at 00:47:18 UTC, Mike Franklin wrote:
On Friday, 24 August 2018 at 00:46:14 UTC, Mike Franklin wrote:
But I need it to implement `memcpy` and `memcmp` in D, so we
can remove the dependency on the D standard library :-)
Gah! What a typo. I mean the C standard
On Friday, 24 August 2018 at 00:58:35 UTC, Guillaume Piolat wrote:
D programs tend to use the C runtime directly, and quite a lot
of it:
https://github.com/search?l=D=%22import+core.stdc%22=Code
I know. They should get that from
https://github.com/D-Programming-Deimos/libc or perhaps even
On Friday, 24 August 2018 at 00:46:14 UTC, Mike Franklin wrote:
It seems, from someone without much historical perspective,
that Phobos was intended to be something like the .Net
Framework for D. Perhaps there are a few fundamentals
(std.algorithm, std.allocator, etc.) to keep, but for the
On Friday, 24 August 2018 at 01:57:03 UTC, Shachar Shemesh wrote:
At this point I can either use the work-around I already have
and (try to, obviously unsuccessfully) forget about it, file a
bug report that will be (justifiably) ignored because no-one
else can reproduce it, or spend an unknown
On Saturday, 18 August 2018 at 13:33:43 UTC, Andrei Alexandrescu
wrote:
A friend recommended this article:
http://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/
I found it awesome and would recommend to anyone in this
community. Worth a close read - no skimming,
On Thursday, 23 August 2018 at 19:48:19 UTC, Robert burner
Schadek wrote:
It is still rough around the corners and
https://issues.dlang.org/show_bug.cgi?id=19084 gives me
somewhat of a hard time, but give it try and scream at me
because it is not nogc.
I've posted a comment on issue 19084
On Thursday, 23 August 2018 at 23:27:51 UTC, Walter Bright wrote:
D deals with it via "chained exceptions", which is terrifyingly
difficult to understand. If you believe it is understandable,
just try to understand the various devious test cases in the
test suite.
I don't think that
On Thursday, 23 August 2018 at 23:06:00 UTC, Ethan wrote:
Is that actually true, or would handling exceptions within the
constructor allow one to initialise the object to an invalid
state and thus still follow RAII paradigms correctly?
If you end up needing to check for that uninitialised
On Thursday, August 23, 2018 7:01:41 PM MDT Mike Franklin via Digitalmars-d
wrote:
> On Friday, 24 August 2018 at 00:58:35 UTC, Guillaume Piolat wrote:
> > D programs tend to use the C runtime directly, and quite a lot
> > of it:
> > https://github.com/search?l=D=%22import+core.stdc%22=Code
>
> I
After working some with Angular and ngrx/store I really came to
like the redux pattern.
Unfortunately, I couldn't find a package on code.dlang.org that
filled that spot when coming back to D.
So I build my own.
It is called reduxed.
If you're interested you can find reduxed here
On Thursday, 23 August 2018 at 10:41:03 UTC, Jonathan M Davis
wrote:
D does have a problem in general of having a lot of great
features that work really well in isolation but don't
necessarily work well in concert (and it doesn't help that some
features have really never been properly
On 8/23/2018 6:22 AM, Shachar Shemesh wrote:
(we used to file bugs in Bugzilla. We stopped doing that because we saw nothing
happens with them)
Quite a number of Weka filed bugs have been fixed.
Here's the 2.080 list of 46 bugs fixed:
https://dlang.org/changelog/2.080.0.html#bugfix-list
The
On 8/23/2018 5:55 AM, Steven Schveighoffer wrote:
If front() returns by ref, then no copying happens. If front() returns by
value, then a copy is made. This should not be surprising behavior.
I think he means, if the range ITSELF doesn't allow copying, it won't work with
foreach (because
On 8/23/2018 9:22 AM, Shachar Shemesh wrote:
So telling me to keep filing them is simply a non-starter. I've got bugs that
simply don't reproduce in watered down examples. I will not spend two days just
to create a test case that demonstrates the bug outside the Weka code base. If
nothing
On Thursday, 23 August 2018 at 07:27:56 UTC, JN wrote:
On Thursday, 23 August 2018 at 06:34:01 UTC, nkm1 wrote:
The only real problem with D is that it's a language designed
with
GC in mind, yet there are numerous attempts to use it without
GC.
Also, supporting GC-less programming gets in the
On 8/23/2018 11:29 AM, Steven Schveighoffer wrote:
What this simply means is your identification of the problem is simply wrong --
it's not that you can't make subtypes with structs (you can), it's that you
can't accept rvalues by reference, and accepting by reference is required for
On Friday, 24 August 2018 at 04:12:42 UTC, Jonathan M Davis wrote:
Unless you're trying to argue for folks dropping Phobos, that's
just not going to fly. Phobos uses libc heavily, and it really
can't do what it needs to do without it (e.g. file operations).
Divorcing druntime from libc may
As some of you may know D frontend was merged into GDC some time
ago and is up to date. D version currently supported by GDC is
2.081.2 and it can be found in "gdc-7" and "gdc-8" branches. I
will say a bit more about GDC development and development plans
later.
I prepared GDC/GCC 7.3.0
I follow a number of official programming language accounts on
Twitter. It is a good way to keep up to date with what's
happening in those communities and I imagine many people do the
same thing.
Something I've noticed is that D is relatively silent on this
front. At least on Twitter, it
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
On 08/23/2018 10:11 PM, Walter Bright wrote:
On 8/23/2018 5:55 AM, Steven Schveighoffer wrote:
[...]
I think he means, if the range ITSELF doesn't allow copying, it won't
work with foreach (because foreach makes a copy), but it will work
with opApply.
foreach (ref v; collection)
does
On Thursday, 23 August 2018 at 21:31:41 UTC, Walter Bright wrote:
My personal opinion is that constructors that throw are an
execrable programming practice, and I've wanted to ban them.
(Andrei, while sympathetic to the idea, felt that too many
people relied on it.) I won't allow throwing
On Thursday, 23 August 2018 at 17:02:12 UTC, Shachar Shemesh
wrote:
On 23/08/18 18:35, Joakim wrote:
[…]
How much time or money exactly has Weka spent on getting this
issue and other "critical" bugs fixed?
Weka is paying prominent D developers as contractors. We've had
David Nadlinger and
On 8/23/2018 3:12 PM, David Nadlinger wrote:
On Thursday, 23 August 2018 at 21:31:41 UTC, Walter Bright wrote:
My personal opinion is that constructors that throw are an execrable
programming practice, and I've wanted to ban them. (Andrei, while sympathetic
to the idea, felt that too many
On Thursday, 23 August 2018 at 23:36:07 UTC, Chris M. wrote:
Heck, now that I'm looking at it, DIP25 seems like a more
restricted form of Rust's lifetimes. Let me know if I'm just
completely wrong about this, but
[snip]
Check out DIP1000
On Thursday, 23 August 2018 at 17:02:12 UTC, Shachar Shemesh
wrote:
How much time or money exactly has Weka spent on getting this
issue and other "critical" bugs fixed?
Weka is paying prominent D developers as contractors. We've had
David Nadlinger and currently employ Johan Engelen. Both
On 8/23/2018 9:19 AM, Jonathan M Davis wrote:
D was designed to have RAII, and it does. It's just that the implementation
is buggy (which is obviously a serious problem), so depending on what your
program is doing, it's not going to work correctly. It's not like we opted
to not have RAII in D,
On Thursday, 23 August 2018 at 19:48:19 UTC, Robert burner
Schadek wrote:
After working some with Angular and ngrx/store I really came to
like the redux pattern.
Unfortunately, I couldn't find a package on code.dlang.org that
filled that spot when coming back to D.
So I build my own.
It is
On Thursday, 23 August 2018 at 22:12:17 UTC, David Nadlinger
wrote:
Throwing constructors are fundamental for making RAII work in a
composable fashion.
Is that actually true, or would handling exceptions within the
constructor allow one to initialise the object to an invalid
state and thus
One takeaway from this is despite my loathing of throwing constructors, they are
a part of D and I need to make them work properly.
I.e. I am not dictating everything in D based on my personal opinions. I try to
pick my battles.
On Thursday, 23 August 2018 at 22:49:32 UTC, Peter Alexander
wrote:
For comparison:
@rustlang:
32.7k followers
12.7k tweets
@D_Programming:
10.1k followers
1k tweets
10,000 is a lot of people to reach, and 1k tweets over 8 years
is too little to seem engaging.
Fair point. Thanks for
On 8/23/2018 3:20 PM, David Nadlinger wrote:
Not to put too fine a point on this, but I don't think I've ever said I couldn't
fix the bug; although I probably did mention it would be better to fix in the
upstream DMD frontend than in LDC.
I would be happy to have a look at it for Weka at this
https://issues.dlang.org/show_bug.cgi?id=18917
Seb changed:
What|Removed |Added
CC||greeen...@gmail.com
--- Comment #3 from Seb ---
On Thursday, 23 August 2018 at 15:48:00 UTC, Chris M. wrote:
On Thursday, 23 August 2018 at 15:14:07 UTC, Steven
Schveighoffer wrote:
On 8/23/18 9:32 AM, Steven Schveighoffer wrote:
[...]
Actually, thinking about this, the shortest lifetime is
dictated by how it is called, so there is no
On Thursday, 23 August 2018 at 23:58:00 UTC, jmh530 wrote:
On Thursday, 23 August 2018 at 23:36:07 UTC, Chris M. wrote:
Heck, now that I'm looking at it, DIP25 seems like a more
restricted form of Rust's lifetimes. Let me know if I'm just
completely wrong about this, but
[snip]
Check out
On Thursday, 23 August 2018 at 23:36:07 UTC, Chris M. wrote:
Heck, now that I'm looking at it, DIP25 seems like a more
restricted form of Rust's lifetimes. Let me know if I'm just
completely wrong about this, but
I think DIP 25 is analogous to Problem #3 for Rust's Non-Lexical
Lifetimes:
On Thursday, 23 August 2018 at 04:46:25 UTC, Eugene Wissner wrote:
But this kind of development doesn't work anymore that well for
commercial customers that aren't (only) interested in research.
From this perspective D becomes over-complicated, half-finished
language. And nobody can tell what
On Thursday, 23 August 2018 at 06:58:13 UTC, Joakim wrote:
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
On Thursday, 23 August 2018 at 07:37:07 UTC, Iain Buclaw wrote:
Symptom: The compiler can't discard unused symbols at compile
time, and so it will spend a lot of time pointlessly optimising
code.
Problem: D has no notion of symbol visibility.
Possible Solution: Make all globals hidden by
On Thursday, 23 August 2018 at 05:37:12 UTC, Shachar Shemesh
wrote:
One that hurt me lately was a way to pass a scoped lazy
argument (i.e. - to specify that the implicit delegate need not
allocate its frame, because it is not used outside the function
call).
I don't see why we just can't
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
On 23/08/2018 7:47 PM, Eugene Wissner wrote:
You can probably solve it like haskell does: Export all symbols by default.
So this module exports everything:
---
module MyModule where
-- My code goes here
---
this one not:
---
module MyModule (symbol1, symbol2) where
On 23/08/18 09:17, Jacob Carlborg wrote:
On Thursday, 23 August 2018 at 05:37:12 UTC, Shachar Shemesh wrote:
One that hurt me lately was a way to pass a scoped lazy argument (i.e.
- to specify that the implicit delegate need not allocate its frame,
because it is not used outside the function
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 well together.
One that hurt me lately was a way to pass
On Thursday, 23 August 2018 at 06:34:01 UTC, nkm1 wrote:
The only real problem with D is that it's a language designed
with
GC in mind, yet there are numerous attempts to use it without
GC.
Also, supporting GC-less programming gets in the way of
improving
D's GC (which is pretty damn bad by
On Thursday, 23 August 2018 at 03:50:44 UTC, Shachar Shemesh
wrote:
And it's not just Weka. I've had a chance to talk in private to
some other developers. Quite a lot have serious, fundamental
issues with the language. You will notice none of them speaks
up on this thread.
They don't see
On 23/08/18 09:04, Mike Franklin wrote:
On Thursday, 23 August 2018 at 03:50:44 UTC, Shachar Shemesh wrote:
And it's not just Weka. I've had a chance to talk in private to some
other developers. Quite a lot have serious, fundamental issues with
the language. You will notice none of them
1 - 100 of 130 matches
Mail list logo
