On Saturday, 4 November 2017 at 13:59:39 UTC, Jonathan M Davis
wrote:
I'm very much of the opinion that proper unit tests pretty much
eliminate the need for out contracts.
I think that sqrt example is just bad. Out contracts shouldn't be
testing specific values, but rather ranges or nullness o
On Wednesday, 1 November 2017 at 18:42:07 UTC, Bo wrote:
There is a issue with Windows. The whole attacking the
messenger, the whole idiotic argumentation's that Windows is
dying, it is all pure useless trolling the people who ask a
simple questions: How to solve the D 64bit issue so that like
On Wednesday, 1 November 2017 at 01:48:13 UTC, codephantom wrote:
Anyway...when you going to give us another surmon?
This is WAY off topic so i'ma just leave it at this post (you can
email me if you want to go further) but I kinda doubt I'll go to
a DConf in Berlin. It is a pain for me. Maybe
On Tuesday, 31 October 2017 at 06:33:02 UTC, Dmitry Olshansky
wrote:
I can live without hot water in my house, would I?
So sad but true... my water heater went down today :( Basement
flooded and it is blinking out a bad vapor sensor error code.
Client applications probably do not care much.
On Tuesday, 31 October 2017 at 01:00:29 UTC, codephantom wrote:
If you play with large databases, containing a lot data, then
64-bit memory addressing will give you access to more memory.
That doesn't really matter. If you're IMPLEMENTING the database,
sure it can help (but is still not *neces
On Monday, 30 October 2017 at 10:53:33 UTC, Kagamin wrote:
Because native.
The processor natively supports all 32 bit code when running in
64 bit more. It just works as far as native hardware goes.
You also need your library dependencies installed too, and indeed
on Linux that might be an e
On Saturday, 28 October 2017 at 16:03:15 UTC, codephantom wrote:
I like seeing how code works in different environments.
The beauty of it is they work basically the same. Especially on
Windows, where 32 bit programs just work on almost any
installation, 32 or 64 bit.
The DMar's C compiler i
On Saturday, 28 October 2017 at 15:36:38 UTC, codephantom wrote:
(if I want to compile 64bit D that is).
(being a recreational programmer
Why do you want 64 bit? I very rarely do 64 bit builds on Windows
(mostly just to make sure my crap actually works) since there's
not actually that many ad
On Thursday, 26 October 2017 at 15:04:52 UTC, Andrei Alexandrescu
wrote:
So I went with the hammer that will fix anything - a string
mixin. Ideas for a nicer solution?
The stdlib has: SetFunctionAttributes in std.traits
http://dpldocs.info/experimental-docs/std.traits.SetFunctionAttributes.1.h
On Saturday, 21 October 2017 at 20:02:28 UTC, user1234 wrote:
I'm not sure that people talked much about the elvis operator
(which was introduced in the topic by M.Nowak). In the first
message were mentioned the null coalescence operator "??"
What's the difference between `?:` and `??`?
As fa
On Friday, 20 October 2017 at 16:36:28 UTC, jmh530 wrote:
It might help to have some sense of how the main devs time on D
is being used.
Definitely, I currently have no clue what they are on.
Is elvis operator more important than improving
safe/scope/nogc/etc, I think most would say no.
I w
On Friday, 20 October 2017 at 09:40:26 UTC, Satoshi wrote:
If you need reason why is writing less code better just
calculate the time of it.
getOne(foo, null) // costs 3 sec.
foo ?? null // cost 1 sec.
Note that I do NOT object to these additions. I think they'd be
trivial, backward compati
On Friday, 20 October 2017 at 00:26:19 UTC, bauss wrote:
return foo ? foo : null;
where
return foo ?? null; would be so much easier.
return getOr(foo, null);
That's really easy to do generically with a function. I wouldn't
object to the ?? syntax, but if it really is something you write
al
On Monday, 16 October 2017 at 09:09:03 UTC, Iain Buclaw wrote:
I would be a lot more worried if something happened to me, if I
were you.
No kidding.
The foundation is irrelevant... it is accumulated knowledge that
we'd lose with someone going away. Walter has a lot of it... but
so do a lot o
On Saturday, 14 October 2017 at 14:35:53 UTC, Shriramana Sharma
wrote:
Hello. I prepared a utility/library to output ANSI escape codes
for terminal text attributes with capabilities as advertised at
https://sites.google.com/site/jamadagni/files/temp/textattr-usage.html. (AFAIK this set of capabi
On Friday, 13 October 2017 at 14:43:41 UTC, jmh530 wrote:
You should be able to that with Adam's jsvar module, no? The
issue is with
No, the D language doesn't allow it at all with structs; even
with mine, you need to `foo(var(0))` or similar (if you define
the function, you could define as
On Friday, 13 October 2017 at 14:22:05 UTC, Meta wrote:
It'd be nice if it did, because I believe it would enable the
following:
I don't think so, since the implicit construction would only work
one level deep. So you can implicit construct the array, but not
the individual variants in the ar
On Friday, 13 October 2017 at 06:33:14 UTC, Jacob Carlborg wrote:
Not sure what the purpose of the latter is.
I think it is just so you can do (T)(T...) in a template and have
it work across more types; unified construction syntax.
Though why it doesn't work with structs is beyond me.
On Tuesday, 10 October 2017 at 16:36:14 UTC, jmh530 wrote:
While I liked when you did the longer stuff, I think even the
slimmed down version has value. It's also probably less work
for you (or someone else if they take it over).
Yeah, I'll post the last couple I generated but never saved.
Th
On Tuesday, 10 October 2017 at 07:12:19 UTC, Eliatto wrote:
I noticed that "This week in D" site was seldom updated. Last
activity is September, the 3rd. If Adam is busy at the moment,
then I think that he should have an assistant.
I generated the file for a couple weeks last month, but I'm no
On Saturday, 7 October 2017 at 20:36:24 UTC, Laeeth Isharc wrote:
Would it make sense to have a BetterC version define for Phobos?
Quite a lot of Phobos already works that way.
On Friday, 15 September 2017 at 06:22:01 UTC, Swoorup Joshi wrote:
I had the same issue trying to use the std.experimental.xml
library.
my dom.d works :P
On Friday, 15 September 2017 at 12:04:27 UTC, Kagamin wrote:
Since width can't be negative, C programmer would use unsigned
integer for it
That's often a big mistake. Lots of people do it... but you
shouldn't, exactly because of the wraparound behavior.
On Wednesday, 13 September 2017 at 15:15:11 UTC, Steven
Schveighoffer wrote:
Shouldn't the bindings be licensed identical to the actual
library code?
The library code isn't being distributed, so I don't think it
matters.
On Monday, 11 September 2017 at 09:56:01 UTC, Jonas Mminnberg
1. receive() pattern matching -- what is common here, always
send (int, someData) where int is a value you compare to. Or
create dummy types that you can match on directly?
I would always create a new type and have it hold the data.
On Sunday, 10 September 2017 at 09:31:55 UTC, Walter Bright wrote:
Yes, we do want to move towards "Better C++" working in an
analogous manner, and that means removing the typeinfo
dependency.
TypeInfo is cheap and useful with classes.
You shouldn't be removing it, just stripping it to the mi
On Saturday, 9 September 2017 at 21:15:10 UTC, EntangledQuanta
wrote:
What's the point then of even having an enum parameter?
You must pass the enum to the enum parameter. Implicit casting
only goes one way.
You are just also allowed to pass the enum to an int parameter.
On Saturday, 9 September 2017 at 20:45:59 UTC, EntangledQuanta
wrote:
unless enum's are implicitly castable to int's
They are, unless you specify some other base type.
https://dlang.org/spec/enum.html#named_enums
See points 3 and 5 there. It will cast to the base type (int by
default), but y
On Saturday, 9 September 2017 at 16:30:51 UTC, Jean-Louis Leroy
wrote:
I did look at the docs, several times, couldn't find it...
you should use my unofficial docs
http://dpldocs.info/version
std.compiler looks useful
http://dpldocs.info/experimental-docs/std.compiler.version_minor.html
sta
On Wednesday, 6 September 2017 at 14:04:56 UTC, Vadim Lopatin
wrote:
Having automatically updated docs hosted on code.dlang.org will
motivate package developers to write better ddoc comments for
their code.
I would go so far as to automatically downvote things with poor
docs...
On Tuesday, 5 September 2017 at 15:46:27 UTC, Laeeth Isharc wrote:
If you want a larger VM email me specs and I will set one up
for you.
My doc generator can eat over 4 gigabytes... but for just minutes
at a time, before going back to 16 megabytes to host plainly
or 2 GB again to host wit
On Tuesday, 5 September 2017 at 18:23:00 UTC, jmh530 wrote:
However, if you use GPL code in a project and want to
distribute it, then you also have to license that project as
GPL.
Which just means your users also promise not to put restrictions
on their users.
It is like the 13th amendment
On Monday, 4 September 2017 at 11:15:08 UTC, Joakim wrote:
While it's an interesting suggestion, dub has 355 open issues,
would be better if more people pitched in on those:
I have zero interest in fixing dub issues since I have zero
interest in using dub.
If one of the libraries were compel
On Friday, 1 September 2017 at 20:17:54 UTC, bitwise wrote:
So I'm thinking now..is this as easy as just figuring out how
it's mangled and calling dlsym()?
Yeah, that's what I was thinking. You can use the .mangleof
property to get the mangle
On Sunday, 27 August 2017 at 18:08:52 UTC, Moritz Maxeiner wrote:
Indeed, but that's only the raw executable, not the full
package (which includes things like syntax highlighting), which
adds another 26MB.
But, yes, Textadept and vim+vim-core (Gentoo speak) are both
gigantic required to bare bo
On Saturday, 26 August 2017 at 23:53:27 UTC, Ryion wrote:
I have the same issue with the Library. The flow of information
is bad, too much walls of text, with too much assumption that
Have you tried my alternative? It is the same content (well it
lags a version or two cuz i haven't updated my
On Saturday, 19 August 2017 at 15:08:41 UTC, rikki cattermole
wrote:
Its called necro-posting.
I'm surprised that post isn't read-only.
Stack Overflow (and sibling sites) explicitly encourage answering
old questions (they will give you badges for it) because they get
good search results and s
On Sunday, 13 August 2017 at 19:50:57 UTC, Roman Hargrave wrote:
But instead I get:
_D8Sequence5Torch12SequenceList6__initZ
_D8Sequence5Torch12SequenceList7__ClassZ
_D8Sequence5Torch12SequenceList6__vtblZ
How are you getting that list? Those particular things are hidden
D specific symbols so
On Wednesday, 9 August 2017 at 22:43:03 UTC, Johnson Jones wrote:
Well, I use Visual D and not sure if it can use rdmd(I'm sure
it can be hacked)
I don't know.
because people cannot cut ties with the past and learn from
their mistakes. Do we even need to separate the linker and
compiler?
On Wednesday, 9 August 2017 at 23:57:19 UTC, Johnson Jones wrote:
Sometimes one doesn't want to import either the whole module
nor specify a single function to import.
There was a proposal called "dependency carrying declarations"
about that, but a library trick was found to beat it:
https:/
On Wednesday, 9 August 2017 at 21:29:07 UTC, Johnson Jones wrote:
I routinely get this error when I forget to add a module that I
import to the project.
You learn it pretty quickly though, don't you?
I guess this is due to the fact that the module does not have a
library backing and the __Mod
On Wednesday, 9 August 2017 at 13:46:29 UTC, MGW wrote:
Memory allocation and deallocation when an application is being
completed in GC operates in FIFO sequence.
Not really, it operates in an undefined sequence... just whenever
it gets around to it in scans.
If destruction order is importan
On Thursday, 3 August 2017 at 12:06:02 UTC, Arafel wrote:
Does somebody know how it's even *supposed* to work?
virtual functions can be overridden. All others work as functions
across shared namespaces. Overloads across namespaces need to be
explicitly added to the overload set, see:
http://
On Thursday, 3 August 2017 at 10:46:06 UTC, Shachar Shemesh wrote:
I seem to remember that D had an option of importing an
external file as something (string? code? anything would do for
my purposes). I cannot seem to find it, however. A search for
"string import" and "import mixin" brought bac
On Friday, 28 July 2017 at 14:58:01 UTC, Ali wrote:
How do you use D?
I use it for everything I can. In the past, I have used it for
work as my main job on web apps, though right now my work usage
of D is limited to helper apps (it has a legacy ruby on rails
codebase I am forced to work with
On Wednesday, 19 July 2017 at 14:09:32 UTC, SrMordred wrote:
Hm, isnt that wrong?
Did my post even go through?
http://forum.dlang.org/post/udaxeyujrafklzpww...@forum.dlang.org
What's going on here is actually pretty simple.
Though calling a destructor on a default-initialized struct
should
On Wednesday, 19 July 2017 at 13:30:56 UTC, sontung wrote:
Thoughts on this sort of feature?
I like it.
On Wednesday, 19 July 2017 at 12:34:50 UTC, Stefan Koch wrote:
Which leaves the scope after assigning.
And therefore triggers the destructor.
No, that's not the case. There is a temporary, but its destructor
is not called. The existing object in `foo` is destroyed, so the
new one can be moved
On Wednesday, 19 July 2017 at 07:48:28 UTC, Danni Coy wrote:
tries to OpAssign foo to itself then calls foo's destructor?
Are you sure that's what's actually happening?
What should be happening there is:
1) it calls Foo's constructor on a temporary location
2) it destroys the old contents of
On Tuesday, 18 July 2017 at 21:35:21 UTC, Moritz Maxeiner wrote:
Could you explain why `return foo();` is even legal for a `void
foo() {}`?
Suppose you are writing a template function that forwards:
auto forward(alias fun, T...)(T args) {
return fun(args);
}
It just saves you from having
On Tuesday, 18 July 2017 at 20:57:51 UTC, Moinak Bhattacharrya
wrote:
Is it possible to mixin function names? IE something like this:
Only if you mixin the entire function.
But what I like to do is to write the function with some internal
name, then do `mixin("alias "~ new_name ~ " =
your_in
On Tuesday, 18 July 2017 at 03:58:49 UTC, Shachar Shemesh wrote:
If you cast a D string to const char* may or may not null
terminate the string.
I do not recommend explicitly casting. This specific case is a
string literal, which is guaranteed to be null terminated and
will implicitly cast.
On Monday, 17 July 2017 at 13:56:24 UTC, Zaheer Ahmed wrote:
I Developed OS in C and C++ but first time stuck in types.
A lot of C and C++ knowledge will carry over to D, but it isn't
exactly the same. D's strings are of type `string` which is
another word for `immutable(char)[]`.
immutable
On Saturday, 15 July 2017 at 16:52:51 UTC, Russel Winder wrote:
D has ???
D has me.
Do not be too proud of the corporate terror the others have
constructed. The power to wave around a million dollars is
insignificant next to the power of the Nerdiness.
On Sunday, 9 July 2017 at 17:13:11 UTC, Dukc wrote:
To answer the part "why" about them sucking, is that they are
generic.
Eh, that's not really why... this is just a crappy
implementation. We can do a lot better with the library and a lot
better with the compiler without losing any of the ge
On Sunday, 9 July 2017 at 17:07:16 UTC, bitwise wrote:
I suppose I'm biased, and PHP/Python have a fair following, but
after a few years of PHP coding (part time as part of a larger
project) I'm not sure I will ever make a full psychological
recovery..
PHP actually is one of the languages tha
On Sunday, 9 July 2017 at 12:56:55 UTC, FoxyBrown wrote:
return str.join(" ");
[...]
Error: template std.array.join cannot deduce function from
argument types !()(string, string)
[...]
simply trying to join a string[] with a separator.
The error message sucks, but you clearly have a string wh
On Sunday, 2 July 2017 at 01:46:14 UTC, Andrei Alexandrescu wrote:
Probably not the problem.
Did you actually try it? Might as well rule it out.
I find building on Windows (including with wine) is an absolute
mess. Have to edit the makefile and it git clones something into
../.. WTF.
On Wednesday, 28 June 2017 at 19:14:19 UTC, aberba wrote:
I'm already using prepared statements thoroughly. strip_tags()
has its own uses beside making it safe for db storage.
prepared statements fight sql injection at save time. HTML
encoding is about fighting XSS when displaying stuff to the
On Tuesday, 27 June 2017 at 17:11:32 UTC, H. S. Teoh wrote:
The cardinal rule of color selection: NEVER only set the
foreground color or the background color alone.
Fun fact: this is why terminal.d's api is `color(fg, bg)` instead
of foregroundColor and backgroundColor independently.
But, I
On Tuesday, 27 June 2017 at 17:41:35 UTC, qznc wrote:
I'm one of the rare people who use a light background in my
terminal (like 99% of websites). It seems only dark backgrounds
are considered, which is understandable.
I also use light backgrounds... so I'm advocating for the light
bg people,
On Tuesday, 27 June 2017 at 14:29:05 UTC, FoxyBrown wrote:
D's error messaging is terrible in some ways. I am trying to
get some code to work and this is the error:
I agree, that error message is terrible, and that's why I have a
PR open to change it.
But this specific case is weird to me to
On Monday, 26 June 2017 at 16:51:06 UTC, Moritz Maxeiner wrote:
As long as you don't introduce immutable by default, resulting
in datastructures being littered with `mutable`.
Yeah, I'm against immutable by default. Also, my nogc, safe, etc
by default idea does NOT apply to main() or virtual m
On Monday, 26 June 2017 at 04:31:33 UTC, H. S. Teoh wrote:
Yes, the wrong defaults were a historical accident.
One that we could fix, even without breaking any code.
Of course, breaking some code to change it would be fairly
straightforward to fix for authors, and could even be done
automati
On Sunday, 25 June 2017 at 23:21:25 UTC, aberba wrote:
Can you share feature(s) in D people are not talking about
which you've found very useful?
I actually like anonymous classes. D took it from Java and D has
a lot of other ways to do it too, but I've found anonymous
classes to be nice with
On Saturday, 24 June 2017 at 18:17:42 UTC, Laeeth Isharc wrote:
what is the barest minimum we need to enable that?
The phobos devs or the dmd packager just have to grab code and
docs they are interested in. It's open source; the author has
already made it available. Drop it in the default imp
On Saturday, 24 June 2017 at 19:22:48 UTC, Ecstatic Coder wrote:
Two lines of code, that's all that's needed to serve an entire
website, with all sorts of files (html, css, js, jpg, png, etc)
located in plenty of directories.
Fun fact: I actually do *not* have code that does that in one
line.
On Saturday, 24 June 2017 at 23:00:59 UTC, Timon Gehr wrote:
Failed to listen on :::80
Listening on port 80 requires root anyway. That's why like my
cgi.d uses 8085 - anything over 1024 can be listened by any user
(and is less likely to have an existing program on it)
On Saturday, 24 June 2017 at 21:04:36 UTC, Ecstatic Coder wrote:
Just rename the three imports into std.*, make this available
at installation, et voilà :)
Or just leave it how it is and let it download the package
automatically!
I'm pretty sure that always works with an out-of-the box dmd
On Friday, 23 June 2017 at 18:26:43 UTC, Ecstatic Coder wrote:
I'm also in favor that some of your personal developments be
converted into std libs.
Eh, std libs is where you lose me. I don't mind offering a "just
works" dmd download on my website, with my packaging dmd for some
particular pu
On Saturday, 24 June 2017 at 12:11:29 UTC, Wulfklaue wrote:
I never considered that D has a bountysource account. Its way,
wy at the bottom of the monthly listing page. It did not
even show up until 3 days ago.
It was somewhat active for a while a couple years ago, but I
found it to be si
On Friday, 23 June 2017 at 13:29:29 UTC, Ecstatic Coder wrote:
But for the remaining, unfortunately this is not as easy, and
this requires some efforts before being able to develop web or
GUI applications.
I'm kinda tempted to offer a pre-packaged compiler download with
my libs and some other
On Wednesday, 21 June 2017 at 15:37:03 UTC, Adam D. Ruppe wrote:
we have a *working* "better C".
I applied my two PRs along with Walter's patch and now have
runtimeless D actually working.
Take a look at this:
// dmd still assumes these are present
// and they are in the C lib, but n
On Wednesday, 21 June 2017 at 20:11:25 UTC, Walter Bright wrote:
All I did was make them do what the host C compiler does.
I propose that the reason the host C compiler does it is because
it is a useful behavior.
If these little strings actually are too large, you can easily
suppress it by
My fav is that familiar code just works.
On Wednesday, 21 June 2017 at 15:37:03 UTC, Adam D. Ruppe wrote:
Then, the last thing from my complaint list (which I wrote in
TWID and emailed to you back October) is that struct
destructors don't work
https://github.com/dlang/dmd/pull/6923
If you want bugzilla entries you can make them
On Tuesday, 20 June 2017 at 04:45:21 UTC, Walter Bright wrote:
Please file bugzilla issues for remaining problems.
I'll do you one better: https://github.com/dlang/dmd/pull/6922
It is a trivial patch to hack fix the big issue I have. Then the
real fix is what Lucia is working on, based on her
On Tuesday, 20 June 2017 at 23:43:47 UTC, Walter Bright wrote:
Those strings eat up space and are of pretty marginal utility.
Don't want to make assert's so bloatsome that people are
discouraged from using them.
Ah, so that's why you exclude the strings in -betterC whose main
reason for exist
On Tuesday, 20 June 2017 at 20:50:14 UTC, Walter Bright wrote:
https://github.com/dlang/dmd/pull/6901
We should generate the default string from the expression for D
too. (at a minimum, I'd actually like to see every variable
printed out too, but this is already written)
Is the rcc from bup.zip now boost licensed too?
If so, I think we should include it in the 32 bit windows setup.
On Tuesday, 20 June 2017 at 03:54:13 UTC, Walter Bright wrote:
Which issue is that?
There isn't a specific bugzilla entry, but the very first one on
your list mentions it:
https://issues.dlang.org/show_bug.cgi?id=11881
and it is caused by typeinfo:
https://issues.dlang.org/show_bug.cgi?id=14
On Tuesday, 20 June 2017 at 01:51:26 UTC, Walter Bright wrote:
Is getting a whole lot better:
It looks to me that this patch does two things:
1) -betterC now implies -defaultlib=
2) -betterC omits the call to _d_dso_registry
And I see a previous patch is also in there that uses C's
`assert`
What is it about Windows that makes you call it a distant
possibility? Is it just that you are unfamiliar with it or is
there some specific OS level feature you plan on needing?
On Sunday, 18 June 2017 at 22:24:47 UTC, Laeeth Isharc wrote:
Yes, but suppose you want to build a C library like Google
snappy, nanomsg or leveldb. It's a bit of a pain on Windows.
Well, that's kinda what I mean by intermediate developer pain...
but there's also lessneed to build libraries o
On Sunday, 18 June 2017 at 21:47:48 UTC, Laeeth Isharc wrote:
Windows has been a bit of a pain, but mostly from the native
code library side.
I've found D on Windows to be very easy for myself and for my end
users... but not for intermediate developers.
For myself, I just set up the necessar
On Sunday, 18 June 2017 at 10:38:49 UTC, Ecstatic Coder wrote:
Something I really appreciate a lot with D is how close it is
to JavaScript.
Have you ever seen my jsvar.d ?
http://forum.dlang.org/thread/kuxfkakrgjaofkrdv...@forum.dlang.org
On Saturday, 17 June 2017 at 21:49:29 UTC, Walter Bright wrote:
It's not quite the same. I spend 99.99% of my time programming
working with code, not makefiles.
I'd say somewhere around 10% of the time I've spent on D pull
requests has been wasted because of the makefiles. It is a
barrier to
On Saturday, 17 June 2017 at 04:32:41 UTC, Liam McGillivray wrote:
I hope that Walter and Andrei give a proper response to this
thread. I wonder why they haven't.
They rarely give definitive answers... except after the fact,
once it is already in master.
On Friday, 16 June 2017 at 03:26:28 UTC, Jonathan Marler wrote:
If you have a better idea on how to implement the bitfields
template that would be great.
The real WTF is that it returns a string in the first place. It
should return a struct.
Here, take a look at this:
-
/++
On Thursday, 15 June 2017 at 22:36:56 UTC, Jonathan Marler wrote:
Doesn't work with eponymous templates, like std.traits.Flag.
For example, make this code work:
That uses `.stringof` which means it is useless for anything
except informational printing.
Post the code you are actually doing (
On Thursday, 15 June 2017 at 21:26:38 UTC, Jonathan Marler wrote:
The common use case is when you'd like to mixin a type when it
is passed to a template.
That's also the most common wrong case. If it is passed to a
template, you have a local name that you should use because it
will work despi
On Thursday, 15 June 2017 at 19:15:55 UTC, Jonathan Marler wrote:
I've found that the fullyQualifiedName template in std.traits
is a good tool for creating mixin code, however, it doesn't
always work.
Why is it useful? I suggest you are probably doing it wrong.
https://stackoverflow.com/quest
On Thursday, 15 June 2017 at 15:01:27 UTC, Jonathan Shamir wrote:
To quote Andrei, if it looks like it should work, it should.
(Also something about turtles).
Hmm, interestingly, even if you explicitly merge the overloads
with `alias foo s.foo;` (which is required btw, see:
http://dlang.org/
On Sunday, 11 June 2017 at 00:28:58 UTC, Andrei Alexandrescu
wrote:
// Also possible (no change to the language)
enum bool isInputRange(R) =
is(typeof((ref R r) => r)) && msg("must be copyable")
Or how about
enum bool isInputRange(R) =
isCopyable!R &&
supportsBoolEmpty!R &&
On Sunday, 11 June 2017 at 00:06:13 UTC, Joakim wrote:
Dev resources are stretched thin as it is, I doubt the core
team would go for it.
I think dev resources are thin because of mismanagement by the
core team failing to attract and retain contributors. Part of
this mismanagement is a really
On Sunday, 4 June 2017 at 04:34:44 UTC, Mike Parker wrote:
I would not have expected enum b = sort(a) to trigger an
allocation. auto b, yes, of course (and the disassembly from
that is not much different). So I'd love to see a blog post
explaining it.
I don't think I can do a full-on blog pos
On Friday, 2 June 2017 at 20:37:05 UTC, H. S. Teoh wrote:
Especially the bit about throwing away years of accumulated
programming work.
Our IRC discussion was more about simplifying the Phobos
interface through breaking changes than actually just dropping
and rewriting. Most the "phobos 2" wo
On Friday, 2 June 2017 at 12:33:17 UTC, Steven Schveighoffer
wrote:
But the perception is going to be that D web frameworks are too
fragile -- one miswritten handler, and your whole webserver
dies.
Correction: "vibe.d frameworks" are fragile. This isn't D
specific - my cgi.d is resilient to t
On Thursday, 1 June 2017 at 10:13:25 UTC, Steven Schveighoffer
wrote:
Which is unfortunate, because vibe.d is a great platform for
web development, other than this. You could go Adam's route and
just put the blinders on, but I think that's not a sustainable
practice.
If you control the deploy
On Wednesday, 31 May 2017 at 13:04:52 UTC, Steven Schveighoffer
wrote:
What are your thoughts? Have you run into this? If so, how did
you solve it?
I don't use vibe, but my cgi.d just catches RangeError, kills the
individual connection, and lets the others carry on. Can you do
the same thing?
201 - 300 of 1278 matches
Mail list logo
