On Monday, 27 August 2012 at 20:46:18 UTC, Jonathan M Davis wrote:
I don't think that I really understand the question, but I'd be
worried about intermixing save with operating on a range as an
output range. It _should_ work, but save was designed with
reading in mind, not writing. An output ra
On Aug 24, 2012, at 1:16 PM, David wrote:
>
> That's not the problem. The problem has nothing to do with the tessellation,
> since the *rendering* is also 1000% slower (when all data is already
> processed).
Is the alignment different between one and the other? I would't think so since
it's d
On Sunday, August 26, 2012 23:20:49 Era Scarecrow wrote:
> On Sunday, 26 August 2012 at 18:07:27 UTC, Jonathan M Davis wrote:
> > But it would be better IMHO to just fix it so that your range
> > is a forward range, since there's no reason for it not to be.
>
> That brings up my own question. I'm
Andrej Mitrovic:
Isn't this limited to just classes?
See the last section of this page:
http://dlang.org/struct.html
Nested Structs: A nested struct is a struct that is declared
inside the scope of a function or a templated struct that has
aliases to local functions as a template argument.
On 8/27/12, bearophile wrote:
>Truly inner structs like Baz
> should have a hidden pointer field that points to the enclosing
> struct.
Isn't this limited to just classes?
On 08/24/2012 11:16 PM, timotheecour wrote:
how to get fully qualified name of a template function?
In the code below I want to get "util.mod.mymethod!(double)"
I tried everything (see below) to no avail, it just returns "mymethod";
The closest I get is demangle(mangledName!(fun)), which shouldn'
monarch_dodra:
What exactly does it mean when you put static in front of a
struct _definition_ (not instance) ?
EG:
static struct S
{
static struct SS
{
}
}
As opposed to
struct S
{
struct SS
{
}
}
For the outer struct S I think it means nothing, it's just the
stupid DMD compi
monarch_dodra:
Either that, or is it considered "best practice" to use "is" to
compare pointers,
For two pointers using "==" or "is" is the same. And I don't
remember "best practices" about this. If your pointers later risk
becoming class references, then it's better to use "is".
Bye,
bear
When comparing pointers, is there any difference when writing:
int* p1, p2;
if(p1 == p2) {...}
if(p1 is p2) {...}
?
My guess would be that no, there isn't *but*:
*Using "==" shows the *intent* of comparing the pointer values?
*Using "is" shows the *intent* of checking if the pointed objects
ar
What exactly does it mean when you put static in front of a
struct _definition_ (not instance) ?
EG:
static struct S
{
static struct SS
{
}
}
As opposed to
struct S
{
struct SS
{
}
}
10 matches
Mail list logo
