On Monday, 27 August 2018 at 20:47:08 UTC, Stefam Koch wrote:
generating it is not the problem but linking it on windows
currently requires the MS linker.
Is that true, though? DMD ships with LLD these days. — David
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
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 user-speci
On Friday, 24 August 2018 at 03:53:38 UTC, David Nadlinger wrote:
[…]
All this is not to say that nothrow constructors aren't a good
idea, though.
This was meant to say nothrow DEstructors, as hopefully obvious
from context. —David
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 stat
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 assessmen
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 cur
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 const
On Saturday, 18 August 2018 at 07:50:04 UTC, Dukc wrote:
On Thursday, 16 August 2018 at 14:11:20 UTC, Andrei
Alexandrescu wrote:
we're working on a HOPL submission.
What's HOPL?
https://hopl4.sigplan.org, presumably. —David
On Tuesday, 31 July 2018 at 18:21:15 UTC, Walter Bright wrote:
What I'm doing is preparing a submission to HOPL on the origins
of D. There's an emphasis on accuracy, references, correct
dates, correct attributions, and correct credit to the right
people.
I'd put together a timeline for my LDC
On Monday, 18 June 2018 at 10:19:57 UTC, Nicholas Wilson wrote:
You should get in contact with Manu Evans, he's working on this
as well IIRC.
Might be a lonely conversation – this is a spam-bot repost of one
of Manu's messages. ;)
—David
On Monday, 11 June 2018 at 03:34:59 UTC, Basile B. wrote:
- default linux:
https://github.com/gcc-mirror/gcc/blob/master/libgcc/memcpy.c
To see what is executed when you call memcpy() on a regular
GNU/Linux distro, you'd want to have a look at glibc instead. For
example, the AVX2 and AVX512 i
On Monday, 11 June 2018 at 08:02:42 UTC, Walter Bright wrote:
On 6/10/2018 9:44 PM, Patrick Schluter wrote:
See what Agner Fog has to say about it:
Thanks. Agner Fog gets the last word on this topic!
Well, Agner is rarely wrong indeed, but there is a limit to how
much material a single pers
On Sunday, 10 June 2018 at 22:23:08 UTC, Walter Bright wrote:
On 6/10/2018 11:16 AM, David Nadlinger wrote:
Because of the large amounts of noise, the only conclusion one
can draw from this is that memcpyD is the slowest,
Probably because it does a memory allocation.
Of course; that was alre
On Sunday, 10 June 2018 at 12:49:31 UTC, Mike Franklin wrote:
I'm not experienced with this kind of programming, so I'm
doubting these results. Have I done something wrong? Am I
overlooking something?
You've just discovered the fact that one can rarely be careful
enough with what is benchma
On Sunday, 27 May 2018 at 06:00:30 UTC, IntegratedDimensions
wrote:
[…] This is a potential suggestion for including such a feature
in the D language to provide sightly more consistency.
Solving this in the general case requires explicitly allowing,
specifying, and tracking covariance and cont
On Wednesday, 16 May 2018 at 14:48:54 UTC, Ethan Watson wrote:
And even better - LDC doesn't support core.simd and has its own
intrinsics that don't match the SSE/AVX intrinsics API
published by Intel.
To provide some context here: LDC only supports the types from
core.simd, but not the __sim
On Saturday, 19 May 2018 at 01:15:10 UTC, RhyS wrote:
More then worth the effort because its used a lot when
discussions are ongoing regarding languages like Go, C, ... Its
one of the best form of free advertisement.
D used to be there, but at some point was at the maintainer's
whim for no sp
On Wednesday, 9 May 2018 at 04:17:17 UTC, Shachar Shemesh wrote:
On 09/05/18 01:09, David Nadlinger wrote:
The algorithm isn't wait-free (haven't thought too carefully
about this, though)
This mirrors a discussion I had with Maor (who originally wrote
it). Let's see if I bring you around the
On Monday, 14 May 2018 at 11:53:44 UTC, Nick Treleaven wrote:
On Monday, 14 May 2018 at 01:20:38 UTC, Jonathan M Davis wrote:
Yeah. It's been discussed that it should be illegal to declare
a struct or class member named init, but that change has yet
to happen.
https://issues.dlang.org/show_bu
On Sunday, 13 May 2018 at 13:37:06 UTC, A. Nicholi wrote:
I am trying to build LDC’s druntime by itself (without phobos)
[…] Make says: “No rule to make target '../dmd/src/osmodel.mak'”
LDC uses its own CMake-based build system for druntime/Phobos,
see runtime/CMakeLists.txt I'm the main repos
On Wednesday, 9 May 2018 at 00:20:39 UTC, Andy Smith wrote:
What's MPSP? :-)
Whoops, MPMC, of course. ;) And that wasn't even the only typo; I
should know better than to post while distracted…
So if any D codebase has got bragging rights on the term
'industry-grade' I think this has to be o
On Tuesday, 8 May 2018 at 17:20:33 UTC, Dmitry Olshansky wrote:
On Tuesday, 8 May 2018 at 04:00:03 UTC, manumaster wrote:
Is there some implement like this in D ?
https://github.com/pramalhe/ConcurrencyFreaks/blob/master/papers/multilist-2017.pdf
Look for Mecca by Wekka.io team. It has great
On Saturday, 7 April 2018 at 09:07:48 UTC, sdvcn wrote:
true?stt="AA":stt="BB";-///Out:BB
writeln(stt);
As I just pointed out in Ali's bug report [1], this is correct, as
true ? stt = "AA" : stt = "BB"
means
(true ? (stt = "AA") : stt) = "BB",
in accordan
On Saturday, 7 April 2018 at 21:22:07 UTC, kdevel wrote:
Can the ternary conditional even be used to assign objects of
the wrong type?
[…]
Congratulations, I'm pretty sure you found an actual bug, even
though it doesn't have anything to do with the conditional
operator per se: https://issues
On Thursday, 1 March 2018 at 14:54:41 UTC, Shachar Shemesh wrote:
I.e. - is it well defined to copy between overlapping slices?
No: https://dlang.org/spec/arrays.html#overlapping-copying
—David
On Tuesday, 13 February 2018 at 23:09:07 UTC, Ali Çehreli wrote:
David (aka klickverbot) is a longtime D contributor […]
… who is slightly surprised at the amount of media interest this
has attracted. ;)
— David
On Monday, 12 February 2018 at 22:35:23 UTC, Walter Bright wrote:
I take it dstep spawns the clang compiler?
It embeds the Clang frontend, which is designed to be usable as a
library.
— David
On Monday, 5 February 2018 at 22:02:09 UTC, Boris-Barboris wrote:
Oh, and look what I just found:
https://github.com/rust-lang/rust/issues/26179
Oh, look:
https://github.com/ldc-developers/druntime/blob/7b77937c70b4aba720e98727dcaad3323c29bd8d/src/ldc/intrinsics.di#L579-L587
— David
On Saturday, 30 December 2017 at 13:48:16 UTC, ChangLong wrote:
After fiber yield, the spoke guard is not able to execute,
unless I throw a exception in Fiber. I am look if there is
some hack method to make the fiber Interrupted at any time with
scope(exit) code executed.
There isn't. In f
On Thursday, 21 December 2017 at 18:40:54 UTC, Andrei
Alexandrescu wrote:
I heard ldc already uses its embedded variant for linking
programs (on Widows? Posix? 32bit? 64bit?)
Internal linking is currently enabled by a separate command-line
flag; we still use the system linker by default (just
On Sunday, 17 December 2017 at 12:45:58 UTC, Yuxuan Shui wrote:
Although this might also be a bug on musl side: it tries to
call init functions even when RTLD_NOLOAD is passed to dlopen.
Ah, interesting. Might be worth reporting as a bug indeed;
without looking too hard, I didn't see anything
On Sunday, 10 December 2017 at 21:00:08 UTC, Timothee Cour wrote:
ldc has better support
Just to be clear, LDC doesn't aim at incrementally "better
support", but support, full stop.
Granted, it has probably seen less real-world use than shared
library support on Linux so there might be some
On Saturday, 9 December 2017 at 00:32:36 UTC, Timothee Cour wrote:
They are on LDC; would be interesting to see whether the
problem occurs there as well (I'm having issues with my Mac
right now, so can't check myself until later).
just updated bug report: same issue with ldc!
Only if not lin
On Friday, 8 December 2017 at 18:59:00 UTC, Manu wrote:
Nicholas wants a *compile* error, not a link error.
I don't think this is necessarily implied from the original post.
Certainly, a linker error would just work fine for the original
use case (avoiding unsupported codegen on compute targe
On Friday, 8 December 2017 at 16:17:14 UTC, Jacob Carlborg wrote:
Well, shared libraries are not officially support on macOS.
They are on LDC; would be interesting to see whether the problem
occurs there as well (I'm having issues with my Mac right now, so
can't check myself until later).
B
On Friday, 17 November 2017 at 02:01:41 UTC, solidstate1991 wrote:
It's filled with Assembly code, and otherwise not very
readable. Would need a lot of work, I don't think it would
worth it. Let's hope that MS will allow us to distribute a
linker alongside DMD.
The more promising avenue would
On Wednesday, 1 November 2017 at 17:24:32 UTC, Igor Shirkalin
wrote:
Does new "-betterC" mean we may use parallelism with using
separate linker?
`-betterC` does not add any emulation of missing platform
features — on the contrary, it *removes* language runtime
functionality! Thus, if TLS does
On Wednesday, 1 November 2017 at 17:30:05 UTC, Iain Buclaw wrote:
GDC supports the same or maybe more platforms than LDC. :-)
Or quite possibly fewer, depending on what one understands
"platform" and "support" to mean. ;)
What is the state of GDC on Android/ARM – has anyone been using
it re
On Wednesday, 21 June 2017 at 16:10:41 UTC, Dan Walmsley wrote:
My idea is to build the whole thing, see what the code size and
performance is, and then one by one reduce things down as
needed.
Starting from nothing so far has been a bit of a none starter!
This way, you'll end up having to p
On Wednesday, 21 June 2017 at 14:53:04 UTC, Dan Walmsley wrote:
when trying to compile I'm getting lots of errors like this one:
C:\dev\repos\druntime\src\gc\impl\manual\gc.d(28): Error:
module config is in file 'gc\config.d' which cannot be read
import path[0] =
C:\Users\danw\AvalonStudio\A
On Tuesday, 20 June 2017 at 17:52:59 UTC, Dan Walmsley wrote:
I need to know, how does the run time know which area of ram to
use for heap?
It uses C's malloc/calloc().
— David
On Tuesday, 20 June 2017 at 19:01:06 UTC, Stefan Koch wrote:
On Tuesday, 20 June 2017 at 18:58:36 UTC, David Nadlinger wrote:
On Tuesday, 20 June 2017 at 17:35:28 UTC, Stefan Koch wrote:
Hit me with brittle numeric code please!
[…]
Unfortunately this also broke the phobos unitttests since now
On Tuesday, 20 June 2017 at 17:35:28 UTC, Stefan Koch wrote:
Hit me with brittle numeric code please!
[…]
Unfortunately this also broke the phobos unitttests since now
more of is attempted to be evaluated.
Just making sure that the Phobos unit tests pass at compile time
(with 64 bit reals, i
On Wednesday, 14 June 2017 at 19:55:49 UTC, Yawniek wrote:
Msgpack rpc with vibe.d works. We used it.
Its extremely fast, youll never get that speed with thrift.
I don't think Thrift is fundamentally much different in
performance than MessagePack, see e.g.
https://github.com/thekvs/cpp-serial
On Wednesday, 14 June 2017 at 12:48:14 UTC, Russel Winder wrote:
On Wed, 2017-06-14 at 10:40 +, gzp via Digitalmars-d wrote:
[…]
cas
in all api I've seen on a failed swap, the current value is
retrieved
(in c/c++ there are intrinsic for them)
This appears to be in core.atomic.
There is a
Hi,
On Tuesday, 13 June 2017 at 06:12:46 UTC, gzp wrote:
the docs are quite minimal
That's true. In fact, this applies not only to atomic intrinsics,
but all of `shared`. We need to sit down and properly specify
things at some point. Andrei has been trying to get an initiative
going to do j
On Sunday, 4 June 2017 at 10:39:09 UTC, rikki cattermole wrote:
Should be a way, since you can pass arg directly via ldc to ld.
But I would expect it to have done it by default anyway.
It is indeed done by default on Windows and Linux. If you dump
the object code before it gets to the linker,
On Saturday, 3 June 2017 at 23:13:09 UTC, Nicholas Wilson wrote:
Good idea, name of global needs to be known in advance though.
Why, and how would that be a non-trivial problem?
— David
On Friday, 2 June 2017 at 21:56:47 UTC, Robert burner Schadek
wrote:
If that works out, the next step is properly to integrate that
in the phobos/druntime/dmd CI. Which properly means putting the
benchmark library through the experimental integration process,
and finding a place for the benchma
On Saturday, 3 June 2017 at 12:13:41 UTC, Nicholas Wilson wrote:
Alas no. __attribute__((target(...)) works because it targeting
different targets of the _same_ backend, this targets different
backends.
But surely you could just take the buffer with the object code
emitted by the compute targ
On Tuesday, 23 May 2017 at 19:47:49 UTC, Andrei Alexandrescu
wrote:
A big one will be making the GC lazily initialize itself.
How detailed are your plans for this? The interaction between GC
and shared library loading is a bit non-trivial to get right.
— David
On Thursday, 11 May 2017 at 21:37:45 UTC, Iain Buclaw wrote:
This is not a problem that needs to be solved for GDC.
It's not a problem that needs to be solved *in* GDC, but it has
to be tackled *for* (packaging) GDC, as you need to have a
bootstrap compiler available. Hence, building a C++-ba
On Thursday, 11 May 2017 at 21:14:16 UTC, Iain Buclaw wrote:
Oh, do you have to do the multi-stage build yourself? I don't.
So you intend to keep a copy of the (old) bootstrap compiler
sources in-tree for all future D-based GDC versions (if/when you
start requiring D)? We could do that just
On Thursday, 11 May 2017 at 20:54:45 UTC, Iain Buclaw wrote:
My rebuttal still stands. Switching build from C++ to D should
be a one line change, if it isn't then you have a problems with
your build process.
How does snap requiring more than a one-line change for a
multi-stage build imply th
On Thursday, 11 May 2017 at 17:56:00 UTC, Iain Buclaw wrote:
I can only infer that you are saying that using a D project
means it's more difficult to get working with snap. To which I
will insert an obligatory "Woah!", and "I expect you to know
better" rebuttal.
...
Woah, I expect you to kn
On Wednesday, 10 May 2017 at 19:46:01 UTC, Joseph Rushton
Wakeling wrote:
Ironically, given that I'd always been worried this would be
the most finnicky compiler snap to create, it's actually the
simplest package definition out of all the Big 3 ;-)
Without even having seen your snap file, I ca
On Saturday, 6 May 2017 at 23:53:45 UTC, Ethan Watson wrote:
This is quite feasible in Europe, since everything is quite
close together. I'm keen. Atila is keen. Anyone else think this
is a great idea?
I'd definitely be interested as well. —David
On Tuesday, 2 May 2017 at 19:34:44 UTC, Marco Leise wrote:
static Phobos2 : 806968 bytes
dynamic Phobos2 : 18552 bytes
That's about 770 KiB to share or 97.7% of its total size!
Awesome!
By the way, using LDC: 402736 bytes for the static build (Linux
x86_64). ;)
— David
On Tuesday, 11 April 2017 at 18:13:11 UTC, Russel Winder wrote:
I have only the data that compiling and linking a GtkD
application against a shared library is a lot shorter than
against a static library.
Sure, but that might be easily fixed, and if you really want to
use shared libraries, you
On Tuesday, 11 April 2017 at 12:03:27 UTC, Matthias Klumpp wrote:
On Monday, 10 April 2017 at 22:15:53 UTC, David Nadlinger wrote:
So do we need to put a reminder about the ABI being unstable
into set of every release notes to make sure we won't get
angry bug reports once users actually build t
On Monday, 10 April 2017 at 22:36:39 UTC, Iain Buclaw wrote:
All the regression fixes and none of the bugs!
That's an interesting approach (spoken with British language
sensibilities).
Is anybody using GDC on a big "modern" D2 codebase
(metaprogramming-heavy, …) right now? From my experienc
On Tuesday, 11 April 2017 at 14:49:03 UTC, Russel Winder wrote:
Having played a bit with GtkD, you always want this as a shared
library for development.
Why would a shared library be preferable to a static library for
that (which might still be re-used between different projects,
etc.)?
—
On Tuesday, 11 April 2017 at 12:38:01 UTC, Matthias Klumpp wrote:
If you could change the SOVERSION with every one of these
changes, or simply just tie it to the respective Phobos
release, distributions would automatically do the right thing
and compile all D code using Phobos against the new v
On Monday, 10 April 2017 at 23:27:35 UTC, Walter Bright wrote:
The next problem is that dmd occasionally changes the interface
to the D runtime. […] I also do not know how the gdc/lds
druntime
interfaces differ.
Just to make this very clear to everybody reading this thread:
It's not even jus
On Monday, 10 April 2017 at 11:40:12 UTC, Matthias Klumpp wrote:
Recompiling the dependency-chain of a software from source when
compiling a package using the "right" compiler and statically
adding the code is forbidden by distro policy.
Yet, from what I could find after a brief search, the Ru
On Monday, 10 April 2017 at 17:27:28 UTC, Matthias Klumpp wrote:
That's why I have been writing a lot of Makefiles and Meson
build definitions lately.
It seems like doing so without having a closer look at the
realities of D software (no stable ABI, etc.) might not have been
the best use of y
On Monday, 10 April 2017 at 17:50:08 UTC, Matthias Klumpp wrote:
I am reading release notes, so we rebuilt dependencies of LDC -
(I assume you mean reverse dependencies.)
[…] But since no bugs were reported, I assume no issues are
present :-)
So do we need to put a reminder about the ABI be
On Monday, 10 April 2017 at 20:43:06 UTC, Iain Buclaw wrote:
Master sports Phobos 2.071. Someone will have to see whether
latter versions can be built using it.
… and some weird Frankensteinian mix of several frontend
versions, I take it, maybe enough to build Phobos, but not
necessarily com
On Wednesday, 5 April 2017 at 16:33:42 UTC, Guillaume Piolat
wrote:
This means TLS is here but uninitialized and eg. core.cpuid has
to be duplicated.
Fragmentation ensues.
You can still lazily initialise TLS data, though. — David
On Wednesday, 5 April 2017 at 14:35:18 UTC, Guillaume Piolat
wrote:
But those of us with the runtime disabled don't have TLS.
This is only true on DMD/OS X x86, where TLS is emulated in
druntime. On other platforms, TLS is implemented by the linker
and/or C runtime, so it works without drunti
On Monday, 3 April 2017 at 21:00:53 UTC, Walter Bright wrote:
The idea of this proposal is to make a nogc program much more
achievable. Currently, in order to not link with the GC, you
can't use exceptions (or at least not in a memory safe manner).
A solution without memory safety is not accept
On Sunday, 2 April 2017 at 10:55:22 UTC, Johan Engelen wrote:
a ~ "abc" "def";
If the order is important, make it `a ~ ("abc" ~ "def")` instead.
I'd argue that with concatenation usually being left-associative,
clearly stating the intention to evaluate the side first would be
a good idea
On Sunday, 5 March 2017 at 15:30:29 UTC, Andrei Alexandrescu
wrote:
Another good thing pointed by the article would be to use the
Mersenne twister for unpredictableSeed, which would make it
difficult to infer the sequence from a few samples. Please
share if that would be a good thing to do.
"
On Friday, 3 March 2017 at 18:11:29 UTC, deadalnix wrote:
https://issues.dlang.org/show_bug.cgi?id=17236
Coming to you on ubuntu soon.
I'm pretty sure that would still work with LDC. So not exactly
"nothing". ;)
– David
On Wednesday, 22 February 2017 at 08:20:41 UTC, Jonathan M Davis
wrote:
Well, the OP's code wrapped the Thread object in another class
and joined the thread in its finalizer, so you would think that
the Thread would be joined before its finalizer was called, but
thinking further on it, IIRC, th
On Wednesday, 22 February 2017 at 07:14:27 UTC, Jonathan M Davis
wrote:
In this particular case, the program would probably exit if you
did
void main()
{
{
auto a = new A;
}
import core.memory;
GC.collect();
}
I very much doubt so. A Thread object isn't just a handle
Hi all,
This year's FOSDEM is taking place Saturday–Sunday in Brussels
(registration-less open source software event).
Any D heads in the area? Kai Nacke is going to give a talk on PGO
in LDC in the LLVM dev room [1], and I'll also be around.
— David
[1] https://fosdem.org/2017/schedule/
On Thursday, 2 February 2017 at 16:08:37 UTC, Profile Anaysis
wrote:
Should be something like […]
Thanks for the suggestion. However, please use
https://issues.dlang.org for bug reports and enhancement
requests. They will just get lost here on the NG.
— David
On Thursday, 2 February 2017 at 09:28:15 UTC, Walter Bright wrote:
I seem to recall Valgrind wasn't on OSX, either, at one point.
Maybe that has since been corrected.
It nominally works on 10.10, if I recall correctly, but not to
the same standard as on Linux.
For C/C++, a combination of the
On Monday, 23 January 2017 at 17:42:00 UTC, Stefan Koch wrote:
interpret3.d passes!!!
The only remaining issues that cause miscompiled code are
UTF(8/16/32) encoding and decoding issues.
Is that without bailing out?
— David
On Wednesday, 19 October 2016 at 03:29:10 UTC, Marco Leise wrote:
I'd say start with DMD, as it comes practically free of
dependencies […]
The same applies to LDC. If you want, you can use the
self-contained binary releases, which just require the system
linker to be present, like DMD does.
On Friday, 14 October 2016 at 13:07:10 UTC, Johan Engelen wrote:
On Friday, 14 October 2016 at 12:55:17 UTC, Guillaume Piolat
wrote:
- this pointer is aligned to N bytes
- this pointer doesn't alias with this pointer
Do you mean these as "just a hint, should not generate invalid
code if not
On Tuesday, 11 October 2016 at 15:08:34 UTC, Andrei Alexandrescu
wrote:
Looked at this, still seems to generate a jump forward with ldc.
ldc.intrinsics.llvm_expect might help to influence basic block
layout.
— David
On Monday, 3 October 2016 at 02:47:09 UTC, Manu wrote:
On 3 October 2016 at 02:37, Timon Gehr via Digitalmars-d
This is a known issue:
https://issues.dlang.org/show_bug.cgi?id=3720
(What I do is: typeof(&typeof(this).f) is int delegate(), but
auto x = &f
does not compile as the 'this' refere
On Sunday, 2 October 2016 at 22:25:14 UTC, Nordlöw wrote:
Where is it?
https://github.com/CyberShadow/digger
— David
On Friday, 30 September 2016 at 14:02:36 UTC, Manu wrote:
Perfect! How can we protect against this going stale?
Don't; just use `ldc2 -help`. This is the perfect example of a
problem that doesn't need a solution. Downloading and extracting
the binary package (or installing the distro package)
On Thursday, 29 September 2016 at 13:58:44 UTC, Eugene Wissner
wrote:
Any chance to get this one working:
import std.typecons;
enum Stuff
{
asdf,
}
void main()
{
BitFlags!Stuff a;
mixin(__traits(fullyQualifiedName, typeof(a)) ~ " c;");
}
This wouldn't be a correct use
On Tuesday, 27 September 2016 at 10:46:23 UTC, Johan Engelen
wrote:
On Monday, 26 September 2016 at 23:32:05 UTC, Walter Bright
wrote:
Linking C libraries and object code into D programs has always
worked easily in D. The other way around, not so well.
[snip]
How much of an issue is this with
On Wednesday, 14 September 2016 at 22:48:29 UTC, Pierre Krafft
wrote:
I've had to use fullyQualifiedName in some string mixins.
Unless there is more to the example than what meets the eye, "had
to" isn't quite true, and even with the `import moduleName!…`
hack, your code is still unnecessaril
On Sunday, 11 September 2016 at 11:33:14 UTC, Dicebot wrote:
On Sunday, 11 September 2016 at 08:37:56 UTC, deadalnix wrote:
On Sunday, 11 September 2016 at 06:09:01 UTC, Dicebot wrote:
Presence of compile-time valid T.init for any type T is
absolutely critical for generic programming and must n
On Saturday, 3 September 2016 at 22:39:22 UTC, Walter Bright
wrote:
Because it's useless to anyone but the compiler devs, and it
adds cruft to the compiler. And even worse than useless, it
confuses the user into thinking it is a meaningful message.
This is short-sighted, for the reason I point
On Sunday, 4 September 2016 at 17:37:28 UTC, David Nadlinger
wrote:
In this case, it's seems to be a race condition between Travis
trying to check out the branch to test, and GitHub actually
serving it up (or you removing it again).
Oh, wait, this is on a branch in the main dlang repo, as crea
On Sunday, 4 September 2016 at 14:46:56 UTC, Andrei Alexandrescu
wrote:
Can we do the same? How can we make sure that a Travis failure
always is legit and needs action?
In this case, it's seems to be a race condition between Travis
trying to check out the branch to test, and GitHub actually
s
On Sunday, 4 September 2016 at 12:37:47 UTC, David Nadlinger
wrote:
Do we, though? It's easy to state a general claim like this,
but I find it hard to actually justify.
(And to pre-empt the collective freak-out, note that this
statement is coming from somebody who has done quite a bit of
pion
On Sunday, 4 September 2016 at 12:33:07 UTC, Andrei Alexandrescu
wrote:
Thanks for answering. Yes, we really need introspection of
private members. One way or another we need to support that.
Do we, though? It's easy to state a general claim like this, but
I find it hard to actually justify.
On Sunday, 4 September 2016 at 00:04:16 UTC, Stefan Koch wrote:
Based on that experience I have now implemented another pseudo
function called __ctfeTicksMs.
[…]
Please tell me what you think.
Please don't. This makes CTFE indeterministic.
To write performance tests, just measure compilation
On Friday, 2 September 2016 at 22:12:20 UTC, Walter Bright wrote:
Compiling with -v will usually show how far the compiler got.
It's curious that this topic should come up now – just a couple
of days ago, I thought about adding better user reporting for LDC
ICEs.
What I was planning to do i
On Friday, 2 September 2016 at 12:15:25 UTC, Manu wrote:
D doesn't seem to have this, and that is proving to be quite
problematic. What's the work around?
Somehow pass in the required information along with the symbol,
for example as a member function/alias or an UDA. It's hard to
get more sp
On Wednesday, 31 August 2016 at 12:45:14 UTC, Ethan Watson wrote:
But in this case, because instantiation happens within the
scope of the binderoo.typedescriptor module instead of within
the scope of the module the template is invoking from, it just
can't see my new CTypeNameOverride specialisa
1 - 100 of 495 matches
Mail list logo
