On Monday, 3 February 2020 at 07:03:03 UTC, Dharmil Patel wrote:
In my code I am using regex like this:
auto rgxComma = regex(r",");
On compiling with dmd v2.076.1, it compiles successfully, but
on compiling with dmd v2.088.1, I am getting lots of errors
like:
/src/phobos/std/regex/i
In my code I am using regex like this:
auto rgxComma = regex(r",");
On compiling with dmd v2.076.1, it compiles successfully, but on
compiling with dmd v2.088.1, I am getting lots of errors like:
/src/phobos/std/regex/internal/thompson.d-mixin-836(837): Error:
template instance
std.r
On Monday, 3 February 2020 at 03:03:20 UTC, Marcone wrote:
On Sunday, 2 February 2020 at 06:03:06 UTC, Marcone wrote:
I like use rdmd when I am programming. But I need that the
program use resource file becouse I am creating program with
gui win32api. How can I add resource when use rdmd?
No
On Sunday, 2 February 2020 at 06:03:06 UTC, Marcone wrote:
I like use rdmd when I am programming. But I need that the
program use resource file becouse I am creating program with
gui win32api. How can I add resource when use rdmd?
No one knows how add resource .res file in rdmd?
On Sunday, 2 February 2020 at 23:48:45 UTC, Paul Backus wrote:
On Sunday, 2 February 2020 at 23:39:10 UTC, ShadoLight wrote:
But, my question was if this was avoidable if braces were not
optional. Paul's answer was that non-optional braces will not
make...
alias a = S!(int);
... non-ambigu
On Sunday, 2 February 2020 at 23:39:10 UTC, ShadoLight wrote:
But, my question was if this was avoidable if braces were not
optional. Paul's answer was that non-optional braces will not
make...
alias a = S!(int);
... non-ambiguous, but I still don't get that based on the
above results.
T
On Sunday, 2 February 2020 at 18:30:17 UTC, Steven Schveighoffer
wrote:
Thanks for taking the time to explain. However, when I tested my
results does not seem to match your explanation.
First, note that:
struct S(T) {}
is *exactly* equivalent to (in fact, you can write it this way,
and i
On 2/2/20 1:57 PM, ag0aep6g wrote:
On 02.02.20 19:49, ag0aep6g wrote:
On 02.02.20 19:18, Steven Schveighoffer wrote:
I'm not sure if I got it right, but like this?
int*[][] g1;
int*[] g2;
int* g3;
void main() @safe
{
/* An array stored on the stack, of referen
On 02.02.20 19:49, ag0aep6g wrote:
On 02.02.20 19:18, Steven Schveighoffer wrote:
I'm not sure if I got it right, but like this?
int*[][] g1;
int*[] g2;
int* g3;
void main() @safe
{
/* An array stored on the stack, of references to heap data: */
int*[3
On 2/2/20 1:32 PM, Dennis wrote:
On Sunday, 2 February 2020 at 18:18:28 UTC, Steven Schveighoffer wrote:
scope should have been a type constructor.
I feel the same way, I find const/immutable much easier to reason about
than scope in its current state.
Do you think scope as a storage class is
On 02.02.20 19:18, Steven Schveighoffer wrote:
On 2/2/20 10:20 AM, ag0aep6g wrote:
[...]
void main() @safe
{
int* a0;
scope int** b0 = &a0; /* accepted */
scope int* a2;
scope int** b2 = &a2; /* rejected */
}
Now it's important to realize tha
On Sunday, 2 February 2020 at 16:29:34 UTC, bauss wrote:
Since he just edited markdown files then it shouldn't matter.
Why? The grep checks explicitly for trailing whitespace in
markdown files.
On Sunday, 2 February 2020 at 18:18:28 UTC, Steven Schveighoffer
wrote:
scope should have been a type constructor.
I feel the same way, I find const/immutable much easier to reason
about than scope in its current state.
Do you think scope as a storage class is fundamentally broken, or
is it s
On 2/2/20 12:51 PM, ShadoLight wrote:
// Should this assertion pass or fail?
static assert(is(a)); //PASS
static assert(is(b)); //FAIL
But I don't see how braces will affect this. Can you explain?
First, note that:
struct S(T) {}
is *exactly* equivalent to (in fact, you can write it this
Thanks for your response.
On Sunday, 2 February 2020 at 15:20:39 UTC, ag0aep6g wrote:
Now it's important to realize that `scope` only applies to the
top-level of the type.
This is where my confusion was.
I knew scope wasn't transitive, so I thought that `scope
string[1]` meant the static arra
On 2/2/20 12:13 PM, cc wrote:
On Friday, 31 January 2020 at 15:47:26 UTC, Steven Schveighoffer wrote:
You could use RefCounted to build a struct that then is sendable with
the data you need. RefCounted allocates using C malloc, not the GC.
Thanks for the tips. How exactly would I go about sen
On 2/2/20 10:20 AM, ag0aep6g wrote:
On 02.02.20 14:40, Dennis wrote:
Compiling the following with -dip1000 gives an error.
```
void main() @safe {
string[1] a0;
scope int[1] a1;
scope string[1] a2;
scope string[] b0 = a0[]; // Fine
scope int[] b1 = a1[]; // Fine
s
On Sunday, 2 February 2020 at 16:23:42 UTC, Paul Backus wrote:
[..]
No, it would still be ambiguous:
struct S(T) {}
alias a = S!(int);
// Should this assertion pass or fail?
static assert(is(a));
Sorry, I don't get it. AFAICS 'is(a)' should return true (since a
is an alias for a full type
On Friday, 31 January 2020 at 15:47:26 UTC, Steven Schveighoffer
wrote:
You could use RefCounted to build a struct that then is
sendable with the data you need. RefCounted allocates using C
malloc, not the GC.
Thanks for the tips. How exactly would I go about sending a
RefCounted value?
st
On Sunday, 2 February 2020 at 12:49:31 UTC, MoonlightSentinel
wrote:
On Sunday, 2 February 2020 at 08:54:02 UTC, mark wrote:
However, four have not been accepted, apparently for technical
reasons. But I don't understand what's wrong or what I need to
do to fix them. (I'm not very knowledgeable
On Sunday, 2 February 2020 at 13:01:26 UTC, ShadoLight wrote:
Not bad and definitely an improvement , but I still find the
inconsistency jarring... IIUC this 'ambiguity' would have been
avoidable if template argument braces were not optional, right?
No, it would still be ambiguous:
struct S(T
On Sunday, 2 February 2020 at 12:49:31 UTC, MoonlightSentinel
wrote:
On Sunday, 2 February 2020 at 08:54:02 UTC, mark wrote:
However, four have not been accepted, apparently for technical
reasons. But I don't understand what's wrong or what I need to
do to fix them. (I'm not very knowledgeable
On 02.02.20 14:40, Dennis wrote:
Compiling the following with -dip1000 gives an error.
```
void main() @safe {
string[1] a0;
scope int[1] a1;
scope string[1] a2;
scope string[] b0 = a0[]; // Fine
scope int[] b1 = a1[]; // Fine
scope string[] b2 = a2[]; // Error: ca
Compiling the following with -dip1000 gives an error.
```
void main() @safe {
string[1] a0;
scope int[1] a1;
scope string[1] a2;
scope string[] b0 = a0[]; // Fine
scope int[] b1 = a1[]; // Fine
scope string[] b2 = a2[]; // Error: cannot take address of
scope local a2
}
On Friday, 31 January 2020 at 15:37:06 UTC, Steven Schveighoffer
wrote:
On 1/30/20 9:10 AM, ShadoLight wrote:
but to give you some historical perspective...
[..]
It was actually much more restrictive before -- e.g. in order
to do an eponymous template, you could have no other members i
On Sunday, 2 February 2020 at 08:54:02 UTC, mark wrote:
However, four have not been accepted, apparently for technical
reasons. But I don't understand what's wrong or what I need to
do to fix them. (I'm not very knowledgeable about github.)
The Travis log suggest that your PRs contain some whi
On Sunday, 2 February 2020 at 08:54:02 UTC, mark wrote:
I've done quite a few small corrections/improvements to the
D-tour's English. Almost all have been accepted.
However, four have not been accepted, apparently for technical
reasons. But I don't understand what's wrong or what I need to
do
I've done quite a few small corrections/improvements to the
D-tour's English. Almost all have been accepted.
However, four have not been accepted, apparently for technical
reasons. But I don't understand what's wrong or what I need to do
to fix them. (I'm not very knowledgeable about github.)
28 matches
Mail list logo
