On Friday, 14 July 2023 at 05:09:58 UTC, Cecil Ward wrote:
On Friday, 14 July 2023 at 05:05:27 UTC, Cecil Ward wrote:
On Friday, 14 July 2023 at 05:03:31 UTC, Cecil Ward wrote:
On Friday, 14 July 2023 at 01:34:54 UTC, Steven Schveighoffer
wrote:
[...]
The way I can see it going is a giant
On Friday, 14 July 2023 at 05:05:27 UTC, Cecil Ward wrote:
On Friday, 14 July 2023 at 05:03:31 UTC, Cecil Ward wrote:
On Friday, 14 July 2023 at 01:34:54 UTC, Steven Schveighoffer
wrote:
[...]
The way I can see it going is a giant template encompassing
pretty much the whole file. Does that
On Friday, 14 July 2023 at 05:03:31 UTC, Cecil Ward wrote:
On Friday, 14 July 2023 at 01:34:54 UTC, Steven Schveighoffer
wrote:
[...]
The way I can see it going is a giant template encompassing
pretty much the whole file. Does that mean that the caller who
calls my one public function does
On Friday, 14 July 2023 at 01:34:54 UTC, Steven Schveighoffer
wrote:
On 7/13/23 8:08 PM, Cecil Ward wrote:
What I really want to do though is provide one single
templated function with the kind of characters / strings as a
parameter. I want to have something like
T Transform( T )( T str)
On 7/13/23 8:08 PM, Cecil Ward wrote:
What I really want to do though is provide one single templated function
with the kind of characters / strings as a parameter. I want to have
something like
T Transform( T )( T str)
called as
auto result = Transform!(dstring)( dstring str );
```d
T[]
Some advice on a couple of points.
I have been working on a module that works on either dchar /
dstrings or wchar / wstrings with just two changes of alias
definitions and a recompile.
What I really want to do though is provide one single templated
function with the kind of characters /
On Thursday, 13 July 2023 at 11:55:17 UTC, Ki Rill wrote:
Why does the first example `class A` work, but the second one
with `class B` does not?
```D
class A {
immutable int a;
this(in int a) {
this.a = a;
}
}
class B {
immutable int[] b;
this(in int[] b) {
On Thursday, 13 July 2023 at 11:55:17 UTC, Ki Rill wrote:
Why does the first example `class A` work, but the second one
with `class B` does not?
```D
class A {
immutable int a;
this(in int a) {
this.a = a;
}
}
class B {
immutable int[] b;
this(in int[] b) {
Why does the first example `class A` work, but the second one
with `class B` does not?
```D
class A {
immutable int a;
this(in int a) {
this.a = a;
}
}
class B {
immutable int[] b;
this(in int[] b) {
this.b = b;
}
}
void main()
{
auto a = new
On Thursday, 13 July 2023 at 11:04:40 UTC, IchorDev wrote:
However, the spec doesn't specify that this is how
`getOverloads` **must** work; is this guaranteed behaviour but
the spec simply omits it?
The order is not guaranteed. I don't know why you need a specific
order, but perhaps you can
On Thursday, 13 July 2023 at 10:53:49 UTC, Dennis wrote:
On Thursday, 13 July 2023 at 08:03:02 UTC, IchorDev wrote:
I've noticed that `__traits(getOverloads)` always returns the
overloads in lexical order across DMD, LDC, and GDC. Is this
reliable at all?
No. It depends on the order the
On Thursday, 13 July 2023 at 08:03:02 UTC, IchorDev wrote:
I've noticed that `__traits(getOverloads)` always returns the
overloads in lexical order across DMD, LDC, and GDC. Is this
reliable at all?
No. It depends on the order the compiler analyzes the symbols,
which is often lexical order,
I've noticed that `__traits(getOverloads)` always returns the
overloads in lexical order across DMD, LDC, and GDC. Is this
reliable at all?
13 matches
Mail list logo
