On 8/24/2018 6:34 AM, Shachar Shemesh wrote:
No, unlike what I suggest, that doesn't work without carefully reviewing every
single place you put it to see whether the constructor actually supports
destructing a partially constructed object.
All D objects are default-initialized before the
On Wednesday, 22 August 2018 at 22:51:58 UTC, Piotrek wrote:
You may already know that from youtube. It seems D starts
getting traction even among musicians:
https://www.youtube.com/watch?v=yCX1Ze3OcKo=youtu.be=64
That really put a smile on my face :D
And it would be a nice example of a D
On Saturday, August 25, 2018 3:30:27 AM MDT Jonathan M Davis via
Digitalmars-d wrote:
> from is not the entire problem, but IMHO, it's definitely the straw that
> breaks the camel's back. It's taking all of this specificity way too far.
> I don't want to have to write or read code that's
On Saturday, 25 August 2018 at 02:25:41 UTC, Walter Bright wrote:
I'm not hostile to debate. I just don't care for "this is
uncharted territory, so let's do nothing" which has been going
on for probably 4 years now, coincident with "scope is
incomplete, D sux".
I.e. lead, follow, or get out
On Friday, 24 August 2018 at 21:57:55 UTC, Meta wrote:
On Friday, 24 August 2018 at 21:53:18 UTC, H. S. Teoh wrote:
I think it's clear by now that most of D's woes are not really
technical in nature, but managerial.
Agreed.
I'm not sure how to improve this situation, since I'm no
manager
On Saturday, 25 August 2018 at 08:02:51 UTC, Jonathan Marler
wrote:
If we defined ':' as the special "from operator" then the
following would be equivalent:
foo.bar:baz
from!"foo.bar".baz
I agree with almost everything you wrote, but I think it would
have to be double ::
foo.bar::baz
On Saturday, August 25, 2018 2:02:51 AM MDT Jonathan Marler via Digitalmars-
d wrote:
> So assuming we're on the same page, you mentioned that the `from`
> template is too verbose. I can see this point. To measure this I
> consider the least verbose syntax for achieving the semantics of
> the
On Saturday, 25 August 2018 at 09:30:27 UTC, Jonathan M Davis
wrote:
On Saturday, August 25, 2018 2:02:51 AM MDT Jonathan Marler via
Digitalmars- d wrote:
[...]
Honestly, I don't want to be doing _anything_ like from with
_any_ syntax. It's not just a question of from itself being too
long.
On Saturday, 25 August 2018 at 04:25:56 UTC, Jonathan M Davis
wrote:
On Friday, August 24, 2018 7:03:37 PM MDT Jonathan Marler via
Digitalmars-d wrote:
> What uses does this actually have, I only see one example
> from the article and it is an oversimplistic example that
> effectively
On Saturday, 25 August 2018 at 07:56:55 UTC, Walter Bright wrote:
On 8/24/2018 6:34 AM, Shachar Shemesh wrote:
No, unlike what I suggest, that doesn't work without carefully
reviewing every single place you put it to see whether the
constructor actually supports destructing a partially
On Friday, 24 August 2018 at 22:04:49 UTC, H. S. Teoh wrote:
I don't know how to reconcile these two. Perhaps if we had the
manpower, we could maintain older versions for long enough to
allow users to gradually rewrite to work with newer compilers,
while the development branch can be bolder
On Friday, 24 August 2018 at 10:58:29 UTC, aliak wrote:
On Friday, 24 August 2018 at 06:41:35 UTC, Jonathan Marler
wrote:
Ever since I read
https://dlang.org/blog/2017/02/13/a-new-import-idiom/ I've
very much enjoyed using the new `from` template. [...]
Of course, if we don't want to encourage
On Saturday, 25 August 2018 at 01:43:19 UTC, Walter Bright wrote:
On 8/24/2018 4:22 PM, tide wrote:
struct SomeStruct
{
void foo() {
// use SomeStruct
}
}
void broken()
{
void function() foo =
foo(); // runtime error, isn't actually safe uses wrong
calling
On Saturday, 25 August 2018 at 10:52:04 UTC, Chris wrote:
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
On Saturday, 25 August 2018 at 02:37:00 UTC, Walter Bright wrote:
On 8/23/2018 5:58 PM, Chris M. wrote:
Seems to be more of a warning of what issues we may face if
DIP25/DIP1000 are finally implemented. It would be good to
consider NLLs as well before D is committed. No point in
repeating
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
I am using Clock.currTime.stdTime to get a unique timestamp in my
program.
Now I need to produce something similar in a different
programming language; so I'm trying to understand how
Clock.currTime works.
According the the documentation Clock.currTime.stdTime should
return the number of
On Saturday, 25 August 2018 at 01:43:19 UTC, Walter Bright wrote:
On 8/24/2018 4:22 PM, tide wrote:
struct SomeStruct
{
void foo() {
// use SomeStruct
}
}
void broken()
{
void function() foo =
foo(); // runtime error, isn't actually safe uses wrong
calling
On Saturday, 25 August 2018 at 12:16:06 UTC, Laeeth Isharc wrote:
Nassim Taleb writes about hormesis. I'm not sure that breakage
of a non-serious kind is necessarily terrible. It might be
terrible for you personally - that's not for me to judge. But
it has the effect of building
On 25.08.2018 03:43, Walter Bright wrote:
On 8/24/2018 4:22 PM, tide wrote:
struct SomeStruct
{
void foo() {
// use SomeStruct
}
}
void broken()
{
void function() foo =
foo(); // runtime error, isn't actually safe uses wrong calling
convention as well
}
Not
On 25/08/18 10:56, Walter Bright wrote:
On 8/24/2018 6:34 AM, Shachar Shemesh wrote:
No, unlike what I suggest, that doesn't work without carefully
reviewing every single place you put it to see whether the constructor
actually supports destructing a partially constructed object.
All D
Hi,
1) I program in C# and I'm wondering if there is something like
?? (Null-Coalescing Operator) in D? (I remember some proposals in
the past).
2) Is possible to create Extensions like in C#?
For example:
public int StrToInt (this string s){
return int.Parse(s);
}
var i =
On Saturday, August 25, 2018 6:53:24 AM MDT Ivo via Digitalmars-d-learn
wrote:
> I am using Clock.currTime.stdTime to get a unique timestamp in my
> program.
> Now I need to produce something similar in a different
> programming language; so I'm trying to understand how
> Clock.currTime works.
>
https://issues.dlang.org/show_bug.cgi?id=19189
Issue ID: 19189
Summary: Accessing private template member allowed
Product: D
Version: D2
Hardware: x86_64
OS: Linux
Status: NEW
Severity: critical
https://issues.dlang.org/show_bug.cgi?id=19148
--- Comment #4 from Joakim ---
Which ldc and DMD versions? Does the just-released LDC 1.11 have this problem?
--
https://issues.dlang.org/show_bug.cgi?id=19190
--- Comment #1 from Yuxuan Shui ---
Sorry, wrong version of the code is attached. Here is the offending code:
struct lr1 {
lr1* a;
}
template proxy(T) {
private alias G = gen!T;
static if (is(typeof(G.str)))
enum str = G.str;
}
https://issues.dlang.org/show_bug.cgi?id=11431
Basile B. changed:
What|Removed |Added
Keywords|rejects-valid |
CC|
https://issues.dlang.org/show_bug.cgi?id=11431
Basile B. changed:
What|Removed |Added
Summary|std.file.slurp with Windows |std.file.slurp fails with
https://issues.dlang.org/show_bug.cgi?id=11431
Basile B. changed:
What|Removed |Added
Keywords||pull
--- Comment #1 from Basile B. ---
pull :
On Saturday, 25 August 2018 at 13:33:58 UTC, SG wrote:
Hi,
1) I program in C# and I'm wondering if there is something like
?? (Null-Coalescing Operator) in D? (I remember some proposals
in the past).
2) Is possible to create Extensions like in C#?
For example:
public int StrToInt (this
https://issues.dlang.org/show_bug.cgi?id=19189
Yuxuan Shui changed:
What|Removed |Added
Summary|Accessing private template |Accessing private member of
Issue filed: https://issues.dlang.org/show_bug.cgi?id=19190
https://issues.dlang.org/show_bug.cgi?id=19190
--- Comment #2 from Yuxuan Shui ---
The behavior of the compiler seems to be sensitive to pragma:
...
// This is the second `gen`
template gen(T: S*, S) {
private alias rc = proxy!S;
pragma(msg, is(typeof(rc.str))); // false
https://issues.dlang.org/show_bug.cgi?id=11052
Basile B. changed:
What|Removed |Added
Keywords||pull
CC|
The offending code base is a little big and hard to reduce. I'll
try if code is required, but here is the gist of the problem:
This snippet of code in my project:
...
alias tmp = genCode!T;
enum str = tmp.str; // This line here
...
Generate a circular reference error.
On 26/08/2018 2:10 AM, Yuxuan Shui wrote:
The offending code base is a little big and hard to reduce. I'll try if
code is required, but here is the gist of the problem:
This snippet of code in my project:
...
alias tmp = genCode!T;
enum str = tmp.str; // This line here
...
On Wednesday, 22 August 2018 at 11:59:37 UTC, Paolo Invernizzi
wrote:
Just found by chance, if someone is interested [1] [2].
/Paolo
[1]
https://gitlab.com/mihails.strasuns/blog/blob/master/articles/on_leaving_d.md
[2]
On Saturday, 25 August 2018 at 13:42:30 UTC, JN wrote:
2) Yes, through UFCS (Uniform Function Call Syntax). It doesn't
require any special syntax, for example:
Very simple indeed.
Thanks.
On Wednesday, 22 August 2018 at 22:51:58 UTC, Piotrek wrote:
You may already know that from youtube. It seems D starts
getting traction even among musicians:
https://www.youtube.com/watch?v=yCX1Ze3OcKo=youtu.be=64
That really put a smile on my face :D
And it would be a nice example of a D
On Saturday, August 25, 2018 7:33:47 AM MDT Shachar Shemesh via Digitalmars-
d wrote:
> On 25/08/18 10:56, Walter Bright wrote:
> > On 8/24/2018 6:34 AM, Shachar Shemesh wrote:
> >> No, unlike what I suggest, that doesn't work without carefully
> >> reviewing every single place you put it to see
On Saturday, 18 August 2018 at 16:47:35 UTC, kinke wrote:
Glad to announce LDC 1.11:
* Based on D 2.081.2.
* Prebuilt packages now using LLVM 6.0.1 and including
additional cross-compilation targets (MIPS, MSP430, RISC-V and
WebAssembly).
* Rudimentary support for compiling & linking directly
https://issues.dlang.org/show_bug.cgi?id=19189
Basile B. changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://issues.dlang.org/show_bug.cgi?id=19190
Issue ID: 19190
Summary: Circular reference error resolved by getting
allMembers
Product: D
Version: D2
Hardware: x86_64
OS: Linux
Status: NEW
Thanks a lot.
The issue was indeed the time zone.
On Saturday, 25 August 2018 at 12:16:06 UTC, Laeeth Isharc wrote:
On Saturday, 25 August 2018 at 10:52:04 UTC, Chris wrote:
On Friday, 24 August 2018 at 19:26:40 UTC, Walter Bright wrote:
There are quite a few different sorts of concerns raised on
this thread and they are linked by how
On Saturday, 25 August 2018 at 14:13:18 UTC, rikki cattermole
wrote:
On 26/08/2018 2:10 AM, Yuxuan Shui wrote:
The offending code base is a little big and hard to reduce.
I'll try if code is required, but here is the gist of the
problem:
This snippet of code in my project:
...
On 2018-08-24 12:09, Uknown wrote:
This is all very nice. I agree that this kind of thing should be a part
of the compiler, but I think it should be a compiler plugin. If dmd had
compiler plugins, I think stuff like this and `dpp` would be much nicer
to use.
We have the front end available
On 8/25/2018 3:52 AM, Chris wrote:
On Friday, 24 August 2018 at 19:26:40 UTC, Walter Bright wrote:
Every programmer who says this also demands new (and breaking) features.
"Every programmer who..." Really?
You want to remove autodecoding (so do I) and that will break just about every D
https://issues.dlang.org/show_bug.cgi?id=11052
Basile B. changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Saturday, 25 August 2018 at 20:52:06 UTC, Walter Bright wrote:
On 8/25/2018 3:52 AM, Chris wrote:
On Friday, 24 August 2018 at 19:26:40 UTC, Walter Bright wrote:
Every programmer who says this also demands new (and
breaking) features.
"Every programmer who..." Really?
You want to remove
On Saturday, 25 August 2018 at 22:55:05 UTC, RhyS wrote:
On Saturday, 25 August 2018 at 12:16:06 UTC, Laeeth Isharc
wrote:
And yet some of the heaviest users of D have said in public
'please break our code". I wonder why that could be.
My answer to that is simply:
Break stuff so it becomes
On 2018-08-22 23:00, kinke wrote:
It could be simpler (and slower ;)) by using `m_flags &
ClassFlags.isCPPclass`.
There's Objective-C classes as well, which does not seem to have an
entry in TypeInfo_Class.ClassFlags.
--
/Jacob Carlborg
On Saturday, 25 August 2018 at 20:17:35 UTC, AN wrote:
I downloaded the script and made it executable. I also have dub
on `/usr/bin/dub` . The example just stalls with no output.
After fidgeting around for 5 minutes I realized it was
downloading silently in the background. (I think for
https://issues.dlang.org/show_bug.cgi?id=13300
Basile B. changed:
What|Removed |Added
CC||b2.t...@gmx.com
--- Comment #5 from Basile B.
https://issues.dlang.org/show_bug.cgi?id=18992
Basile B. changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Saturday, 25 August 2018 at 20:52:06 UTC, Walter Bright wrote:
If I fix the bug, I break existing code, and apparently a
substantial amount of existing code. What's your advice on how
to proceed with this?
At least for the transition period, I'd have attributes only
apply to the
On Saturday, 25 August 2018 at 22:55:05 UTC, RhyS wrote:
Be honest, how many people will use BetterC in production!
Much, MUCH more likely than that I would ever use full D with GC
in production.
Really, if I want a language with a GC, D is not that good. Why
wouldn't I use a JVM language
https://issues.dlang.org/show_bug.cgi?id=19148
--- Comment #5 from Yuxuan Shui ---
(In reply to Joakim from comment #4)
> Which ldc and DMD versions? Does the just-released LDC 1.11 have this
> problem?
Most recent ldc release fix the build problem. But this is a dmd bug
nonetheless.
This bug
On 2018-08-25 15:33, SG wrote:
Hi,
1) I program in C# and I'm wondering if there is something like ??
(Null-Coalescing Operator) in D? (I remember some proposals in the past).
Not in the language but it can be implemented as a library function by
overloading "opDispatch". See [1] for an
https://issues.dlang.org/show_bug.cgi?id=19191
Issue ID: 19191
Summary: Memory allocation failure with -profile=gc and dynamic
array of opaque handles
Product: D
Version: D2
Hardware: x86_64
OS: Windows
On 8/25/2018 7:37 AM, Jonathan M Davis wrote:
In general, any place where D was
designed around the idea that something would _always_ be there (e.g. init
values and default initialization) but we've then later added the ability to
get around it (e.g. void initialization or @disable) has tended
I downloaded the script and made it executable. I also have dub
on `/usr/bin/dub` . The example just stalls with no output. After
fidgeting around for 5 minutes I realized it was downloading
silently in the background. (I think for homepage examples, they
should be running in verbose mode as
On 8/25/2018 6:32 AM, Timon Gehr wrote:
(Or at least, not wrong. Using e.g. `void*`
instead of an incompatible type would already be an improvement.)
Making it void* is a reasonable idea.
On Sat, Aug 25, 2018 at 10:10 PM Anonymouse via Digitalmars-d-announce <
digitalmars-d-announce@puremagic.com> wrote:
> On Friday, 24 August 2018 at 08:30:35 UTC, Daniel Kozak wrote:
> > On Friday, 24 August 2018 at 05:35:13 UTC, Eugene Wissner wrote:
> >> As some of you may know D frontend was
On Saturday, 25 August 2018 at 20:59:56
[...]
Thanks for supporting us on Arch, Daniel!
On Friday, 24 August 2018 at 17:12:53 UTC, H. S. Teoh wrote:
I got bitten by this just yesterday. Update dmd git master,
update vibe.d git master, now my vibe.d project doesn't compile
anymore due to some silly string.d error somewhere in one of
vibe.d's dependencies. :-/
Welcome to my life
On 8/25/2018 2:46 PM, David Nadlinger wrote:
On Saturday, 25 August 2018 at 20:52:06 UTC, Walter Bright wrote:
If I fix the bug, I break existing code, and apparently a substantial amount
of existing code. What's your advice on how to proceed with this?
At least for the transition period, I'd
On Saturday, 25 August 2018 at 20:19:44 UTC, Walter Bright wrote:
On 8/25/2018 6:32 AM, Timon Gehr wrote:
(Or at least, not wrong. Using e.g. `void*` instead of an
incompatible type would already be an improvement.)
Making it void* is a reasonable idea.
If/when (I really hope the latter)
On 8/25/2018 6:33 AM, Shachar Shemesh wrote:
If you allow a feature to be disabled, you really need to keep in mind that
feature might be well and truly disabled.
Disabling default initializations is not @safe, and that means taking
responsibility for it not being default initialized.
It's
On Friday, 24 August 2018 at 08:30:35 UTC, Daniel Kozak wrote:
On Friday, 24 August 2018 at 05:35:13 UTC, Eugene Wissner wrote:
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"
On Saturday, 25 August 2018 at 20:28:55 UTC, Chris M. wrote:
On Saturday, 25 August 2018 at 20:17:35 UTC, AN wrote:
I downloaded the script and made it executable. I also have
dub on `/usr/bin/dub` . The example just stalls with no
output. After fidgeting around for 5 minutes I realized it was
https://issues.dlang.org/show_bug.cgi?id=11052
Basile B. changed:
What|Removed |Added
Severity|normal |enhancement
--- Comment #2 from Basile B. ---
On Saturday, 25 August 2018 at 20:37:04 UTC, Everlast wrote:
On Saturday, 25 August 2018 at 20:28:55 UTC, Chris M. wrote:
On Saturday, 25 August 2018 at 20:17:35 UTC, AN wrote:
I downloaded the script and made it executable. I also have
dub on `/usr/bin/dub` . The example just stalls with no
On Saturday, 25 August 2018 at 20:52:06 UTC, Walter Bright wrote:
I.e. a nothrow constructor now must call a throwing destructor.
This is not some made up example, it breaks existing code:
https://github.com/dlang/dmd/pull/6816
If I fix the bug, I break existing code, and apparently a
On Saturday, 25 August 2018 at 20:59:56 UTC, Daniel Kozak wrote:
Hmm I am not sure, but how long did you have this gdc package
installed? It
seems I forgot to update .SRCINFO. There should be gdc-8.2.0-2
which has
2.081.1 d frontend.
I will fix this on monday, until than you can uninstall gdc
On Friday, 24 August 2018 at 17:36:25 UTC, Matthew OConnor wrote:
I'd like to run a sequence of executables with something like
std.process.execute, but I would like the sequence to error out
if one of the executables returns a non-zero return code. What
is the recommended way to do this? A
On Saturday, 25 August 2018 at 22:00:47 UTC, JN wrote:
It's kind of a dirty and not very portable solution, but if you
run by executeShell, you could so something like
executeShell("cmd1 && cmd2 && cmd3") and let the shell do the
sequence for you.
Oops, didn't notice it was suggested
On Saturday, 25 August 2018 at 12:16:06 UTC, Laeeth Isharc wrote:
And yet some of the heaviest users of D have said in public
'please break our code". I wonder why that could be.
My answer to that is simply:
Break stuff so it becomes STABLE! Remove junk and clutter.
Do NOT break stuff to add
On Saturday, 25 August 2018 at 23:46:54 UTC, Radu wrote:
I think you need to look at Dlang as what it is - still WIP and
mostly *community driven*.
I got used to the occasional breaking or regression, and the
best I can advise is to try to report or fix them if you can.
There are still
https://issues.dlang.org/show_bug.cgi?id=19148
--- Comment #8 from Joakim ---
OK, if you're so sure it's a problem in dmd's backend, a pull request is
welcome.
--
On Saturday, 25 August 2018 at 22:53:44 UTC, Walter Bright wrote:
On 8/25/2018 2:46 PM, David Nadlinger wrote:
At least for the transition period, I'd have attributes only
apply to the user-specified code and infer them for the actual
full constructor. (We can still print a deprecation warning
void print()
{
}
void print(T, A...)(T t, A a)
{
import std.stdio;
writeln(t);
print(a);
}
The problem is, suppose one wants to specify A
void print(T, int... A)(T t, A a)
while tricks can be used, why doesn't D support such an obvious
syntax? We can specify an arbitrary type but
On Wednesday, 22 August 2018 at 11:59:37 UTC, Paolo Invernizzi
wrote:
Just found by chance, if someone is interested [1] [2].
/Paolo
[1]
https://gitlab.com/mihails.strasuns/blog/blob/master/articles/on_leaving_d.md
[2]
On 26/08/2018 7:08 AM, Jacob Carlborg wrote:
On 2018-08-24 12:09, Uknown wrote:
This is all very nice. I agree that this kind of thing should be a
part of the compiler, but I think it should be a compiler plugin. If
dmd had compiler plugins, I think stuff like this and `dpp` would be
much
https://issues.dlang.org/show_bug.cgi?id=19148
--- Comment #7 from Yuxuan Shui ---
(In reply to Joakim from comment #6)
> There was an issue with a ldc header mismatch that kinke found when merging
> the 2.081 frontend into ldc: are you sure that's not what you're seeing
> instead?
>
>
On Sunday, 26 August 2018 at 02:26:58 UTC, Everlast wrote:
The problem is, suppose one wants to specify A
void print(T, int... A)(T t, A a)
while tricks can be used, why doesn't D support such an obvious
syntax? We can specify an arbitrary type but can't restrict it
in an obvious way, in
https://issues.dlang.org/show_bug.cgi?id=13416
--- Comment #12 from Joakim ---
Sorry, only seeing your question now. I was simply checking the D tests on
FreeBSD back then but I haven't used that OS in years, so can't look into it
further now.
--
https://issues.dlang.org/show_bug.cgi?id=19148
--- Comment #6 from Joakim ---
There was an issue with a ldc header mismatch that kinke found when merging the
2.081 frontend into ldc: are you sure that's not what you're seeing instead?
88 matches
Mail list logo
