On Sunday, 15 June 2014 at 21:38:18 UTC, Dmitry Olshansky wrote:
15-Jun-2014 20:21, Dicebot пишет:
On Saturday, 14 June 2014 at 16:34:35 UTC, Dmitry Olshansky
wrote:
But let's face it - it's a one-time job to get it right in
your
favorite build tool. Then you have fast and cached (re)build.
On Saturday, 14 June 2014 at 16:34:35 UTC, Dmitry Olshansky wrote:
Consider something like REST API generator I have described
during
DConf. There is different code generated in different contexts
from same
declarative description - both for server and client. Right
now simple
fact that you
15-Jun-2014 20:21, Dicebot пишет:
On Saturday, 14 June 2014 at 16:34:35 UTC, Dmitry Olshansky wrote:
But let's face it - it's a one-time job to get it right in your
favorite build tool. Then you have fast and cached (re)build.
Comparatively costs of CTFE generation are paid in full during
On Thursday, 12 June 2014 at 16:42:38 UTC, Dmitry Olshansky wrote:
It's always nice to ask something on D NG, so many good answers
I can hardly choose whom to reply ;) So this is kind of
broadcast.
Yes, the answer seems spot on - reflection! But allow me to
retort.
I'm not talking about
On 6/14/14, 8:05 AM, Dicebot wrote:
Adoption - yes. Production usage - less so (though still important).
Difference between 1 second and 5 seconds is very important. Between 10
seconds and 1 minute - not so much.
Wait, what? -- Andrei
On Saturday, 14 June 2014 at 15:25:11 UTC, Andrei Alexandrescu
wrote:
On 6/14/14, 8:05 AM, Dicebot wrote:
Adoption - yes. Production usage - less so (though still
important).
Difference between 1 second and 5 seconds is very important.
Between 10
seconds and 1 minute - not so much.
Wait,
14-Jun-2014 19:05, Dicebot пишет:
On Thursday, 12 June 2014 at 16:42:38 UTC, Dmitry Olshansky wrote:
[snip]
Well, I'm biased by heavy-handed ones. Say I have a (no longer) secret
plan of doing a next-gen parser generator in D. Needless to say swaths
of non-trivial code generation. I'm all for
11-Jun-2014 22:03, Atila Neves пишет:
On Tuesday, 10 June 2014 at 19:36:57 UTC, bearophile wrote:
At about 40.42 in the Thoughts on static regex there is written
even compile-time printf would be awesome. There is a patch about
__ctWrite in GitHug, it should be fixed and merged.
Bye,
12-Jun-2014 03:29, Adam D. Ruppe пишет:
On Wednesday, 11 June 2014 at 18:03:06 UTC, Atila Neves wrote:
I wish I'd taken the mic at the end, and 2 days later Adam D. Ruppe
said what I was thinking of saying: unit test and debug the CTFE
function at runtime and then use it at compile-time when
Dmitry Olshansky:
Unless things improve dramatically CTFE code generation +
An alternative and much faster JITter for LLVM, something like
this could make CTFE on LDC2 very quick:
http://llvm.org/devmtg/2014-04/PDFs/LightningTalks/fast-jit-code-generation.pdf
Bye,
bearophile
On Thursday, 12 June 2014 at 09:17:45 UTC, Dmitry Olshansky wrote:
12-Jun-2014 03:29, Adam D. Ruppe пишет:
On Wednesday, 11 June 2014 at 18:03:06 UTC, Atila Neves wrote:
I wish I'd taken the mic at the end, and 2 days later Adam D.
Ruppe
said what I was thinking of saying: unit test and debug
Am 12.06.2014 11:17, schrieb Dmitry Olshansky:
This one thing I'm loosing sleep over - what precisely is so good in
CTFE code generation in_practical_ context (DSL that is quite stable,
not just tiny helpers)?
By the end of day it's just about having to write a trivial line in your
favorite
On Tuesday, 10 June 2014 at 17:19:42 UTC, Dicebot wrote:
On Tuesday, 10 June 2014 at 15:37:11 UTC, Andrei Alexandrescu
wrote:
Watch, discuss, upvote!
https://news.ycombinator.com/newest
https://twitter.com/D_Programming/status/476386465166135296
On 06/12/14 11:17, Dmitry Olshansky via Digitalmars-d-announce wrote:
This one thing I'm loosing sleep over - what precisely is so good in CTFE
code generation in _practical_ context (DSL that is quite stable, not just
tiny helpers)?
Language integration; direct access to meta data (such as
On Thursday, 12 June 2014 at 09:17:45 UTC, Dmitry Olshansky wrote:
This one thing I'm loosing sleep over - what precisely is so
good in CTFE code generation in _practical_ context (DSL that
is quite stable, not just tiny helpers)?
By the end of day it's just about having to write a trivial
On Thursday, 12 June 2014 at 10:40:56 UTC, Colin wrote:
Maybe a change to the compiler to write any mixin'd string out
to a temporary file (along with some identifier information and
the line of code that generated it) and at the next compilation
time try reading it back from that file iff the
On Thursday, 12 June 2014 at 12:31:09 UTC, Dicebot wrote:
On Thursday, 12 June 2014 at 10:40:56 UTC, Colin wrote:
Maybe a change to the compiler to write any mixin'd string out
to a temporary file (along with some identifier information
and the line of code that generated it) and at the next
On 06/12/2014 02:31 PM, Dicebot wrote:
Compiler can cache return value of function that get called from inside
mixin statement (for a given argument set). As CTFE is implicitly pure
(no global state at compile-time) later generated code can be simply
re-used for same argument set.
Re-using it
On Thursday, 12 June 2014 at 12:49:23 UTC, Timon Gehr wrote:
On 06/12/2014 02:31 PM, Dicebot wrote:
Compiler can cache return value of function that get called
from inside
mixin statement (for a given argument set). As CTFE is
implicitly pure
(no global state at compile-time) later generated
On Thursday, 12 June 2014 at 09:17:45 UTC, Dmitry Olshansky wrote:
This one thing I'm loosing sleep over - what precisely is so
good in CTFE code generation in _practical_ context (DSL that
is quite stable, not just tiny helpers)?
I've asked this same question before and my answer is mostly
12-Jun-2014 16:25, Dicebot пишет:
On Thursday, 12 June 2014 at 09:17:45 UTC, Dmitry Olshansky wrote:
This one thing I'm loosing sleep over - what precisely is so good in
CTFE code generation in _practical_ context (DSL that is quite stable,
not just tiny helpers)?
By the end of day it's just
On 6/12/14, 4:04 AM, dennis luehring wrote:
you should write a big top post about your CTFE experience/problems - it
is important enough
yes please
On Thursday, 12 June 2014 at 08:42:49 UTC, Dmitry Olshansky wrote:
11-Jun-2014 22:03, Atila Neves пишет:
On Tuesday, 10 June 2014 at 19:36:57 UTC, bearophile wrote:
At about 40.42 in the Thoughts on static regex there is
written
even compile-time printf would be awesome. There is a patch
On Tuesday, 10 June 2014 at 19:36:57 UTC, bearophile wrote:
At about 40.42 in the Thoughts on static regex there is
written even compile-time printf would be awesome. There is a
patch about __ctWrite in GitHug, it should be fixed and merged.
Bye,
bearophile
I wish I'd taken the mic at the
On Wednesday, 11 June 2014 at 18:03:06 UTC, Atila Neves wrote:
I wish I'd taken the mic at the end, and 2 days later Adam D.
Ruppe said what I was thinking of saying: unit test and debug
the CTFE function at runtime and then use it at compile-time
when it's ready for production.
Aye. It
Watch, discuss, upvote!
https://news.ycombinator.com/newest
https://twitter.com/D_Programming/status/476386465166135296
https://www.facebook.com/dlang.org/posts/863635576983458
http://www.reddit.com/r/programming/comments/27sjxf/dconf_2014_day_1_talk_4_inside_the_regular/
Andrei
On Tuesday, 10 June 2014 at 15:37:11 UTC, Andrei Alexandrescu
wrote:
Watch, discuss, upvote!
https://news.ycombinator.com/newest
https://twitter.com/D_Programming/status/476386465166135296
https://www.facebook.com/dlang.org/posts/863635576983458
At about 40.42 in the Thoughts on static regex there is written
even compile-time printf would be awesome. There is a patch
about __ctWrite in GitHug, it should be fixed and merged.
Bye,
bearophile
28 matches
Mail list logo
