On Wednesday, 15 March 2017 at 21:10:49 UTC, Laeeth Isharc wrote:
A Jupyter kernel exists - written by John Colvin. It works and
I have used it, and you can write python in one sell and D in
another. It needs some work though, and so I am sure if
somebody would like to contribute pull reque
On Saturday, 4 March 2017 at 19:36:30 UTC, Jon Degenhardt wrote:
On Saturday, 4 March 2017 at 09:13:15 UTC, Seb wrote:
On Friday, 3 March 2017 at 19:18:31 UTC, jmh530 wrote:
A Jupyter kernel would go a long way to students being able
to easily play around with it in a browser. There's already
On Monday, 6 March 2017 at 14:49:42 UTC, Atila Neves wrote:
On Monday, 6 March 2017 at 05:50:01 UTC, Rico Decho wrote:
It's actually rather rare to *need* to avoid the GC -- only
niche applications need that, like if you're writing a game
engine that has to avoid stop-the-world pauses (which ca
On Tuesday, 7 March 2017 at 16:26:20 UTC, Russel Winder wrote:
Learn the lesson from Java. It started with a truly crap GC and
everyone said Java is crap because the GC is garbage. D has
seemingly actually progressed beyond this stage technically but
not marketing wise. The Java folk worked o
On 03/15/2017 11:50 AM, Stefan Koch wrote:
Wish I could get rid of the need for "mixin(...)" in interp though.
But you can.
in interp you can evoke the function you generate however for that you
need to pass s to it.
Thus reinventing writef and defeating the whole point of interpolated
stri
On Tuesday, 28 February 2017 at 23:29:24 UTC, Jared Jeffries
wrote:
I've read the answer to questions like "Which is the best
programming language to learn in 2017?".
Nobody was telling anything about D, which is really sad,
because in my opinion D could be one of the best answers to
this que
On Wednesday, 15 March 2017 at 16:11:44 UTC, Stefan Koch wrote:
and string-foreach caused dmd to miscomplie itself ... *sigh*
Guess what ?
Things work so much better when you allocate space for the zero
terminator :)
The segfaults are mysteriously gone :D
On Wednesday, 15 March 2017 at 19:00:21 UTC, Nordlöw wrote:
On Wednesday, 15 March 2017 at 15:59:46 UTC, Stefan Koch wrote:
Unsupported Features include :
- Unicode/Auto-decoding support.
NOTE: foreach(char c; string) { ... } will work since it does
not auto-decode.
- Floating point.
- Cl
On Wednesday, 15 March 2017 at 18:52:16 UTC, H. S. Teoh wrote:
On Wed, Mar 15, 2017 at 03:59:46PM +, Stefan Koch via
Digitalmars-d wrote: [...]
Unsupported Features include :
[...]
- Floating point.
[...]
- unions
[...]
What are the chances / what's the expected timeframe of unions
On Wednesday, 15 March 2017 at 15:59:46 UTC, Stefan Koch wrote:
Unsupported Features include :
- Unicode/Auto-decoding support.
NOTE: foreach(char c; string) { ... } will work since it does
not auto-decode.
- Floating point.
- Classes
- unions
- structs containing other structs.
- array
On Wed, Mar 15, 2017 at 01:50:28PM +, Inquie via Digitalmars-d wrote:
> I hate building code strings for string mixins as it's very ugly and seems
> like a complete hack.
>
> How bout, instead, we have a special code string similar to a multiline
> string that allows us to represent valid D co
On Wed, Mar 15, 2017 at 03:59:46PM +, Stefan Koch via Digitalmars-d wrote:
[...]
> Unsupported Features include :
[...]
> - Floating point.
[...]
> - unions
[...]
What are the chances / what's the expected timeframe of unions being
implemented?
Support for unions in CTFE is a MAJOR mileston
Am Wed, 15 Mar 2017 08:27:23 +
schrieb Suliman :
> On Tuesday, 14 March 2017 at 20:21:44 UTC, aberba wrote:
> > Amazon S3 seem like a common solution for object storage these
> > days[1] but I'm seeing almost no activity in this area (stable
> > native D API). Why?
> >
> > [1] https://trends
On Tue, Mar 14, 2017 at 07:21:05PM -0700, Jonathan M Davis via Digitalmars-d
wrote:
> On Tuesday, March 14, 2017 11:38:21 H. S. Teoh via Digitalmars-d wrote:
[...]
> > Actually, come to think of it, the only time isNarrowString, et al
> > are *necessary* is in the autodecoding parts of Phobos. I
On Wednesday, 15 March 2017 at 15:59:46 UTC, Stefan Koch wrote:
On Wednesday, 15 March 2017 at 15:49:59 UTC, Nordlöw wrote:
On Wednesday, 15 March 2017 at 13:49:43 UTC, Stefan Koch wrote:
String Slicing is in!
Great! What remains?
Unsupported Features include :
- Unicode/Auto-decoding sup
On Wednesday, 15 March 2017 at 15:49:59 UTC, Nordlöw wrote:
On Wednesday, 15 March 2017 at 13:49:43 UTC, Stefan Koch wrote:
String Slicing is in!
Great! What remains?
Unsupported Features include :
- Unicode/Auto-decoding support.
NOTE: foreach(char c; string) { ... } will work since it do
On Wednesday, 15 March 2017 at 15:39:38 UTC, Nick Sabalausky
(Abscissa) wrote:
On 03/15/2017 09:50 AM, Inquie wrote:
e.g.,
string s = "smile";
enum code1 = @#
void happyCode = "Makes me @@s@@";
#@
enum code2 = code1 ~ @#
int ImThisHappy = @@s.length@@;
#@
mixin(code);
import scriptlike; /
On Wednesday, 15 March 2017 at 13:49:43 UTC, Stefan Koch wrote:
String Slicing is in!
Great! What remains?
On 03/15/2017 05:02 AM, Jonathan M Davis via Digitalmars-d wrote:
If you want a cheap solution for running a website, there's always digital
ocean:
https://www.digitalocean.com/
You can run whatever you want on there quite easily. It's what I use when I
want to spin up a server for something o
On Wednesday, 15 March 2017 at 14:58:02 UTC, Ethan Watson wrote:
On Wednesday, 15 March 2017 at 13:37:41 UTC, Andrea Fontana
wrote:
It seems pretty easy to use with dstep, isn't it?
I need to use it at compile time. Linking as a C lib is
subsequently out of the question.
For now, yes :)
I
On 03/15/2017 09:50 AM, Inquie wrote:
e.g.,
string s = "smile";
enum code1 = @#
void happyCode = "Makes me @@s@@";
#@
enum code2 = code1 ~ @#
int ImThisHappy = @@s.length@@;
#@
mixin(code);
import scriptlike; // https://github.com/Abscissa/scriptlike
string s = "smile";
// http://semitwi
On Wednesday, 15 March 2017 at 13:37:41 UTC, Andrea Fontana wrote:
It seems pretty easy to use with dstep, isn't it?
I need to use it at compile time. Linking as a C lib is
subsequently out of the question.
On Wednesday, 15 March 2017 at 14:12:57 UTC, Adam D. Ruppe wrote:
On Wednesday, 15 March 2017 at 13:50:28 UTC, Inquie wrote:
I hate building code strings for string mixins as it's very
ugly and seems like a complete hack.
Me too, that's why I avoid doing it.
Check out my tips of the week here
On 03/02/2017 02:32 PM, Andrei Alexandrescu wrote:
Worth a look: https://github.com/dlang/druntime/pull/1781. This moves
comparison code away from tedious runtime-introspected routines to nice
templates. -- Andrei
Another notable PR in the same vein:
https://github.com/dlang/druntime/pull/1792
On 15/03/17 15:50, Inquie wrote:
I hate building code strings for string mixins as it's very ugly and
seems like a complete hack.
What I usually do is use the q{} format. Vim does syntax highlighting on it:
string code = q{
immutable int a = %s;
}.format(something);
...
mixin(
On Wednesday, 15 March 2017 at 13:50:28 UTC, Inquie wrote:
I hate building code strings for string mixins as it's very
ugly and seems like a complete hack.
Me too, that's why I avoid doing it.
Check out my tips of the week here:
http://arsdnet.net/this-week-in-d/sep-20.html
and here:
http://a
On Wednesday, 15 March 2017 at 13:50:28 UTC, Inquie wrote:
I hate building code strings for string mixins as it's very
ugly and seems like a complete hack.
How bout, instead, we have a special code string similar to a
multiline string that allows us to represent valid D code. The
compiler can
I hate building code strings for string mixins as it's very ugly
and seems like a complete hack.
How bout, instead, we have a special code string similar to a
multiline string that allows us to represent valid D code. The
compiler can then verify the string after compilation to make
sure it i
On Thursday, 16 February 2017 at 21:05:51 UTC, Stefan Koch wrote:
[ ... ]
String Slicing is in!
The following code will now compile with newCTFE.
string slice(string s, uint lwr, uint upr)
{
return s[lwr .. upr];
}
static assert(slice("Hello World", 6, 11) == "World");
On Wednesday, 15 March 2017 at 13:23:00 UTC, deadalnix wrote:
On Wednesday, 15 March 2017 at 13:14:31 UTC, deadalnix wrote:
This is making the history very spaghettified. Is that
possible to have the bot rebase/squash commits and then
pushing ?
Arf I fat fingered the title, i meant the dlang
On Wednesday, 15 March 2017 at 13:26:45 UTC, Ethan Watson wrote:
https://github.com/google/cityhash
Does anyone know of a D implementation of Google's Cityhash? My
google-fu has failed me and I've been unable to find one.
It seems pretty easy to use with dstep, isn't it?
https://github.com/google/cityhash
Does anyone know of a D implementation of Google's Cityhash? My
google-fu has failed me and I've been unable to find one.
On Wednesday, 15 March 2017 at 13:14:31 UTC, deadalnix wrote:
This is making the history very spaghettified. Is that possible
to have the bot rebase/squash commits and then pushing ?
Arf I fat fingered the title, i meant the dlang bot.
This is making the history very spaghettified. Is that possible
to have the bot rebase/squash commits and then pushing ?
On Wednesday, 15 March 2017 at 09:57:52 UTC, aberba wrote:
There are several options:
1. Heroku Paas with s3
2. Docker Datacenter with your own image with dlanguage/dmd
image as base.
3. Or hosting yourself on AWS or linode or digitaloceon. AWS is
generally safe for small team with less resour
On Wednesday, 15 March 2017 at 09:02:54 UTC, Jonathan M Davis
wrote:
https://www.digitalocean.com/
You can run whatever you want on there quite easily. It's what
I use when I want to spin up a server for something online.
- Jonathan M Davis
or for $2,50 on https://www.vultr.com/
On Wednesday, 15 March 2017 at 08:27:23 UTC, Suliman wrote:
On Tuesday, 14 March 2017 at 20:21:44 UTC, aberba wrote:
Amazon S3 seem like a common solution for object storage these
days[1] but I'm seeing almost no activity in this area (stable
native D API). Why?
[1] https://trends.builtwith.c
On Tuesday, 14 March 2017 at 21:09:23 UTC, Adam D. Ruppe wrote:
On Tuesday, 14 March 2017 at 20:21:44 UTC, aberba wrote:
Amazon S3 seem like a common solution for object storage these
days[1] but I'm seeing almost no activity in this area (stable
native D API). Why?
I've done it before, but n
On Tuesday, 14 March 2017 at 20:38:37 UTC, ikod wrote:
On Tuesday, 14 March 2017 at 20:21:44 UTC, aberba wrote:
Amazon S3 seem like a common solution for object storage these
days[1] but I'm seeing almost no activity in this area (stable
native D API). Why?
[1] https://trends.builtwith.com/cd
On Wednesday, March 15, 2017 08:27:23 Suliman via Digitalmars-d wrote:
> On Tuesday, 14 March 2017 at 20:21:44 UTC, aberba wrote:
> > Amazon S3 seem like a common solution for object storage these
> > days[1] but I'm seeing almost no activity in this area (stable
> > native D API). Why?
> >
> > [1]
On Tuesday, 14 March 2017 at 20:21:44 UTC, aberba wrote:
Amazon S3 seem like a common solution for object storage these
days[1] but I'm seeing almost no activity in this area (stable
native D API). Why?
[1] https://trends.builtwith.com/cdn/Amazon-S3
How much the lowest vibed ready instance c
41 matches
Mail list logo
