Submitted
https://issues.dlang.org/show_bug.cgi?id=18058
On 10/12/17 14:07, Shachar Shemesh wrote:
On 10/12/17 14:00, Shachar Shemesh wrote:
On 10/12/17 13:44, Jonathan M Davis wrote:
it sounds like the delegate that's
being generated isn't @nogc, so it can't be called within the function,
whi
On Monday, 11 December 2017 at 04:57:44 UTC, Ivan Trombley wrote:
Any SDL experts out there that can give me a clue?
I've used SDL quite a bit, but can't help with your specific
problem. However, I suggest you try the new(ish) SDL forums for
stuff like this. It's particularly off topic here
Experimenting with compositing images in SDL2, I get a dark edge
around my textures. In the image below, you can see the top
example where I composite the cyan image on top of the
blue/magenta image looks correct but the bottom example, which is
done using SDL_RenderCopy is not correct.
http:
On 12/10/2017 6:22 AM, meppl wrote:
I think these are wrong criterias to estimate the value of commonmark.
Commonmark doesn't need to list anyone and doesn't need to be listed by anyone
to be a standard. commonmark is a standard proven by following "facts":
1) whenever a language feature is used
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 Sunday, 10 December 2017 at 21:00:08 UTC, Timothee Cour wrote:
Supporting shared libraries seems like a pretty important
issue, IMO more important than many things being worked on. I
can't think of other languages not supporting them; it renders
many use cases impossible, preventing more wid
Supporting shared libraries seems like a pretty important issue, IMO
more important than many things being worked on. I can't think of
other languages not supporting them; it renders many use cases
impossible, preventing more widespread adoption.
Is it on the roadmap? It's been a very long standin
On Sunday, 10 December 2017 at 06:20:43 UTC, Walter Bright wrote:
On 12/9/2017 9:17 PM, meppl wrote:
since commonmark exists, is specified and is compatibale to
many markdown-languages, I claim there is a markdown
standard: http://spec.commonmark.org/
It certainly wants to be the standard, b
On Sunday, 10 December 2017 at 11:44:20 UTC, Jonathan M Davis
wrote:
On Sunday, December 10, 2017 12:54:00 Shachar Shemesh via
Digitalmars-d wrote:
void func1(scope lazy string msg) @nogc {
}
void func2(scope lazy string msg) @nogc {
func1(msg);
}
What? Why is msg GC allocating, especiall
On Saturday, 9 December 2017 at 10:36:08 UTC, Messenger wrote:
On Saturday, 9 December 2017 at 09:38:05 UTC, IM wrote:
For purposes of debugging, I'm using writeln() to print stuff
out from tasks running concurrently on many threads. At some
point it crashes with the following stack trace:
Th
On Saturday, 9 December 2017 at 05:07:46 UTC, Elronnd wrote:
Note to anyone trying to implement this (I might try, but I
don't have the expertise to...):
http://wiki.osdev.org/D_Bare_Bones,
http://wiki.osdev.org/D_barebone_with_ldc2, and
https://github.com/PowerNex/PowerNex
Remember that the
On 10/12/17 14:00, Shachar Shemesh wrote:
On 10/12/17 13:44, Jonathan M Davis wrote:
it sounds like the delegate that's
being generated isn't @nogc, so it can't be called within the function,
which would be a completely different issue from allocating a closure.
Here's the thing, though. There
On 10/12/17 13:44, Jonathan M Davis wrote:
it sounds like the delegate that's
being generated isn't @nogc, so it can't be called within the function,
which would be a completely different issue from allocating a closure.
Here's the thing, though. There is no reason for the delegate to be
calle
On Sunday, December 10, 2017 12:54:00 Shachar Shemesh via Digitalmars-d
wrote:
> void func1(scope lazy string msg) @nogc {
> }
>
> void func2(scope lazy string msg) @nogc {
> func1(msg);
> }
>
> What? Why is msg GC allocating, especially since I scoped the lazy? Why
> is msg even evaluated?
>
On Sunday, 10 December 2017 at 02:31:47 UTC, Jonathan M Davis
wrote:
On Sunday, December 10, 2017 02:02:31 Dave Jones via
Digitalmars-d wrote:
https://issues.dlang.org/show_bug.cgi?id=14984
Honestly, it would have never occurred to me to try and modify
the variables declared in the foreach l
void func1(scope lazy string msg) @nogc {
}
void func2(scope lazy string msg) @nogc {
func1(msg);
}
What? Why is msg GC allocating, especially since I scoped the lazy? Why
is msg even evaluated?
Something seems off here.
Thanks,
Shachar
On 12/08/2017 05:13 AM, Walter Bright wrote:
I just don't see much of any improvement of markdown over LINK2.
I do.
17 matches
Mail list logo
