On Monday, 5 March 2018 at 10:57:35 UTC, Jonathan M Davis wrote:
Here's something I wrote up on const:
http://jmdavisprog.com/articles/why-const-sucks.html
I suppose that it's not exactly the most positive article, but
I feel that it's accurate.
- Jonathan M Davis
Its amazing how typed lan
On Monday, 5 March 2018 at 13:59:02 UTC, Adam D. Ruppe wrote:
On Monday, 5 March 2018 at 10:57:35 UTC, Jonathan M Davis wrote:
Here's something I wrote up on const:
And then, of course, like you said "don't use it" is the
solution to most of the const system's flaws anyway which
seems to
On Monday, 5 March 2018 at 10:57:35 UTC, Jonathan M Davis wrote:
Here's something I wrote up on const:
http://jmdavisprog.com/articles/why-const-sucks.html
I suppose that it's not exactly the most positive article, but
I feel that it's accurate.
- Jonathan M Davis
Spot on article, and touc
On Tuesday, 6 March 2018 at 07:39:00 UTC, aberba wrote:
On Tuesday, 6 March 2018 at 04:31:42 UTC, Nick Sabalausky
(Abscissa) wrote:
[...]
I'm not opposed to it being added, but I'm not aware of what
benefit it would provide that would big enough to make it a
priority. Also, AFAIK, vibe doesn't
On Monday, 5 March 2018 at 10:57:35 UTC, Jonathan M Davis wrote
(in the article):
The problem is that the entire object must be fully initialized
before
the body of the postblit constructor is run. That means that
any member
variables which are const or immutable are stuck at whatever
they were
On Tuesday, 6 March 2018 at 10:49:48 UTC, Dukc wrote:
On Monday, 5 March 2018 at 10:57:35 UTC, Jonathan M Davis wrote
(in the article):
The problem is that the entire object must be fully
initialized before
the body of the postblit constructor is run. That means that
any member
variables which
On Tuesday, 6 March 2018 at 00:08:33 UTC, psychoticRabbit wrote:
On Monday, 5 March 2018 at 23:40:35 UTC, Atila Neves wrote:
I'd have a snowball's chance in hell convincing anyone at a
"regular" company of adopting D if anyone there even imagined
any of the above could happen.
We have to do
On Tuesday, 6 March 2018 at 06:53:30 UTC, Adam Wilson wrote:
On 3/5/18 15:40, Atila Neves wrote:
On Monday, 5 March 2018 at 17:47:13 UTC, Seb wrote:
On Monday, 5 March 2018 at 15:16:14 UTC, Atila Neves wrote:
On Saturday, 3 March 2018 at 01:50:25 UTC, Martin Nowak
wrote:
[...]
Is is just me
On Tuesday, 6 March 2018 at 11:03:24 UTC, Nemanja Boric wrote:
title = title.dup;// doesn't work anymore
Strange! You're right it does not when the type declares a member
as const, yet:
On Monday, 5 March 2018 at 10:57:35 UTC, Jonathan M Davis
wrote (in the article):
And if an objec
On 3/6/18 1:49 AM, Jonathan M Davis wrote:
Regardless, I doubt that the design of ranges is going to be changed at this
point given the amount of code that would break as a result, and these sort
of changes are not backwards compatible.
I sometimes think we would be better off to drop InputRan
On 3/5/18 6:40 PM, Atila Neves wrote:
On Monday, 5 March 2018 at 17:47:13 UTC, Seb wrote:
On Monday, 5 March 2018 at 15:16:14 UTC, Atila Neves wrote:
On Saturday, 3 March 2018 at 01:50:25 UTC, Martin Nowak wrote:
Glad to announce D 2.079.0.
This release comes with experimental `@nogc` excepti
On Tuesday, 6 March 2018 at 12:05:26 UTC, Dukc wrote:
I think we have a bug here. I believe postblits should behave
like constructors in both events.
https://issues.dlang.org/show_bug.cgi?id=18561
On 3/6/18 2:11 AM, Jonathan M Davis wrote:
On Tuesday, March 06, 2018 05:34:39 psychoticRabbit via Digitalmars-d-
announce wrote:
On Tuesday, 6 March 2018 at 05:22:58 UTC, Void-995 wrote:
Can somebody explain how &array[0] is more safe than array.ptr?
Just want to understand why second statemen
On Sunday, 4 March 2018 at 22:37:21 UTC, kinke wrote:
Thanks to all contributors!
And thanks to Johan Engelen and Joakim for putting together an
announcement for the blog!
https://dlang.org/blog/2018/03/06/ldc-1-8-0-released/
Reddit:
https://www.reddit.com/r/programming/comments/82f9wk/ld
On Tuesday, 6 March 2018 at 14:06:54 UTC, Mike Parker wrote:
On Sunday, 4 March 2018 at 22:37:21 UTC, kinke wrote:
Thanks to all contributors!
And thanks to Johan Engelen and Joakim for putting together an
announcement for the blog!
https://dlang.org/blog/2018/03/06/ldc-1-8-0-released/
R
On Tuesday, 6 March 2018 at 10:02:10 UTC, Radu wrote:
On Monday, 5 March 2018 at 10:57:35 UTC, Jonathan M Davis wrote:
Here's something I wrote up on const:
http://jmdavisprog.com/articles/why-const-sucks.html
I suppose that it's not exactly the most positive article, but
I feel that it's acc
On Tuesday, 6 March 2018 at 01:46:26 UTC, Mike Parker wrote:
On Monday, 5 March 2018 at 19:40:12 UTC, Stephan wrote:
Hello fellow Dlers,
thanks to last years DConf some German D developers agreed to
meet for drinks in Hamburg.
What time?
To get this thread on the first page for a long time,
On Tuesday, 6 March 2018 at 03:21:47 UTC, Nick Sabalausky
(Abscissa) wrote:
Wait, seriously? Phobos frequently passes ranges by value?
You *should* pass most ranges by value, just like how you should
rarely use `ref T[]` or `T[]*`. Ranges, like slices, are
typically already small references t
On Tuesday, March 06, 2018 15:23:52 Adam D. Ruppe via Digitalmars-d-announce
wrote:
> On Tuesday, 6 March 2018 at 03:21:47 UTC, Nick Sabalausky
>
> (Abscissa) wrote:
> > Wait, seriously? Phobos frequently passes ranges by value?
>
> You *should* pass most ranges by value, just like how you should
On Sunday, 4 March 2018 at 22:37:21 UTC, kinke wrote:
Hi everyone,
on behalf of the LDC team, I'm glad to announce LDC 1.8. The
highlights of this version in a nutshell:
* Based on D 2.078.3.
* New switch `-link-defaultlib-shared` to link against shared
druntime/Phobos.
* Plugins support, c
On Tuesday, 6 March 2018 at 07:11:24 UTC, Jonathan M Davis wrote:
That example actually should be perfectly @safe, because the
array is null, and it's using writeln. Dereferencing null is
@safe, because it segfaults and thus can't corrupt memory or
access invalid memory. You obviously don't w
On Tuesday, 6 March 2018 at 15:23:52 UTC, Adam D. Ruppe wrote:
On Tuesday, 6 March 2018 at 03:21:47 UTC, Nick Sabalausky
(Abscissa) wrote:
The definition of "what is a forward/non-forward range" for
struct-based ranges should have been "is this() @disabled
(non-forward range), or is this() enab
On 3/6/18 11:13 AM, psychoticRabbit wrote:
(I assume that int is meant to be size_t)
Yes, I changed the uncommented one to auto after I realized, but not the
commented one ;)
-Steve
On Tuesday, 6 March 2018 at 15:44:14 UTC, Martin Tschierschke
wrote:
On Sunday, 4 March 2018 at 22:37:21 UTC, kinke wrote:
Hi everyone,
on behalf of the LDC team, I'm glad to announce LDC 1.8. The
highlights of this version in a nutshell:
* Based on D 2.078.3.
* New switch `-link-defaultlib-
On Tuesday, 6 March 2018 at 15:39:41 UTC, Jonathan M Davis wrote:
[snip]
How well Phobos has done with this has improved over time as
more and better testing has been added (testing for reference
type ranges is probably the most critical to finding this
particular problem), but I doubt that P
On Tuesday, 6 March 2018 at 16:54:59 UTC, Joakim wrote:
[...]
Nothing new, unfortunately, though you can follow progress here:
https://github.com/ldc-developers/ldc/issues/2153
I plan to spend some time on it, but have been putting it off.
Thank you!
On Tue, Mar 06, 2018 at 08:39:41AM -0700, Jonathan M Davis via
Digitalmars-d-announce wrote:
[...]
> Yeah. If you're dealing with generic code rather than a specific range
> type that you know is implicitly saved when copied, you have to use
> save so often that it's painful, and almost no one doe
On Mon, Mar 05, 2018 at 10:21:47PM -0500, Nick Sabalausky (Abscissa) via
Digitalmars-d-announce wrote:
> On 03/05/2018 12:38 PM, H. S. Teoh wrote:
> >
> > This broke the by-value assumption inherent in much of Phobos code,
>
> Wait, seriously? Phobos frequently passes ranges by value? I sincerel
On Tuesday, March 06, 2018 09:36:43 H. S. Teoh via Digitalmars-d-announce
wrote:
> Andrei has said before, and probably on more than one occasion, that if
> he were to redesign ranges today, one of the things he would do
> differently was to change the definition of forward range so that .save
> i
On Tuesday, March 06, 2018 09:41:42 H. S. Teoh via Digitalmars-d-announce
wrote:
> As they say, hindsight is always 20/20. But it wasn't so easy to
> foresee the consequences at the time when the very concept of ranges was
> still brand new.
Except that even worse, I'd argue that hindsight reall
On Tue, Mar 06, 2018 at 11:20:56AM -0700, Jonathan M Davis via
Digitalmars-d-announce wrote:
> On Tuesday, March 06, 2018 09:41:42 H. S. Teoh via Digitalmars-d-announce
> wrote:
> > As they say, hindsight is always 20/20. But it wasn't so easy to
> > foresee the consequences at the time when the
On 3/6/18 10:39 AM, Jonathan M Davis wrote:
Yeah. If you're dealing with generic code rather than a specific range type
that you know is implicitly saved when copied, you have to use save so often
that it's painful, and almost no one does it. e.g.
equal(lhs.save, rhs.save)
or
immutable result
On Saturday, 3 March 2018 at 07:37:38 UTC, Nick Sabalausky
(Abscissa) wrote:
An all-D MySQL/MariaDB client library:
https://github.com/mysql-d/mysql-native
==
Tagged 'v2.1.0', which mainly adds a few new features,
including greatly simplified shortcut syn
On Tuesday, 6 March 2018 at 18:31:08 UTC, bauss wrote:
On Saturday, 3 March 2018 at 07:37:38 UTC, Nick Sabalausky
(Abscissa) wrote:
[...]
I'm unsure how I'd go about implementing prepared statements in
a vibe.d application correctly.
[...]
Like more specifically do I still call lockConnec
On Tue, Mar 06, 2018 at 01:31:39PM -0500, Steven Schveighoffer via
Digitalmars-d-announce wrote:
> On 3/6/18 10:39 AM, Jonathan M Davis wrote:
> > Yeah. If you're dealing with generic code rather than a specific
> > range type that you know is implicitly saved when copied, you have
> > to use save
On Tuesday, March 06, 2018 10:47:36 H. S. Teoh via Digitalmars-d-announce
wrote:
> On Tue, Mar 06, 2018 at 01:31:39PM -0500, Steven Schveighoffer via
Digitalmars-d-announce wrote:
> > On 3/6/18 10:39 AM, Jonathan M Davis wrote:
> > > Yeah. If you're dealing with generic code rather than a specifi
On Tuesday, 6 March 2018 at 18:36:45 UTC, bauss wrote:
On Tuesday, 6 March 2018 at 18:31:08 UTC, bauss wrote:
On Saturday, 3 March 2018 at 07:37:38 UTC, Nick Sabalausky
(Abscissa) wrote:
[...]
I'm unsure how I'd go about implementing prepared statements
in a vibe.d application correctly.
[
On Tuesday, 6 March 2018 at 18:17:58 UTC, Jonathan M Davis wrote:
I'm not actually convinced that killing auto-decoding is really
much better.
I don't think the problem is auto-decoding in string range
adapters, but repeated validation.
https://issues.dlang.org/show_bug.cgi?id=14519#c32
If yo
On Tuesday, March 06, 2018 19:06:25 Martin Nowak via Digitalmars-d-announce
wrote:
> On Tuesday, 6 March 2018 at 18:17:58 UTC, Jonathan M Davis wrote:
> > I'm not actually convinced that killing auto-decoding is really
> > much better.
>
> I don't think the problem is auto-decoding in string range
On Monday, 5 March 2018 at 17:38:52 UTC, H. S. Teoh wrote:
struct Container {
auto opSlice() const {
static struct Result {
private Container impl;
private int n; // internal mutable st
On Tuesday, 6 March 2018 at 12:21:41 UTC, Steven Schveighoffer
wrote:
That being said, I'm wondering if it wouldn't be better to have
std.experimental be in its own repository.
Just showing that phobos is not the right place to develop
modules/packages, also mir.
IMO std.experimental provides
On Tuesday, 6 March 2018 at 11:10:49 UTC, Atila Neves wrote:
The problem with that is I was waiting for 2.079.0 since it
fixes a bug that prevented me from upgrading to any of the
2.078.x releases on Windows.
I think 2.078 would make an excellent starting point for a LTS
because of the import
On Monday, 5 March 2018 at 16:18:11 UTC, Chris M. wrote:
Good stuff. Still bothers me that we had to special case "throw
new Exception();" in order to make it nogc. I can't think of
any better ways right now
Implementing EH for values (instead of class references) would
have been a lot more c
On Tuesday, 6 March 2018 at 05:22:58 UTC, Void-995 wrote:
Can somebody explain how &array[0] is more safe than array.ptr?
Just want to understand why second statement isn't allowed in
safe anymore.
&array[0] is runtime bounds-checked
array.ptr is unchecked and might return an out-of-bounds poi
On 3/6/18 2:30 PM, Martin Nowak wrote:
On Tuesday, 6 March 2018 at 12:21:41 UTC, Steven Schveighoffer wrote:
But if needed, you could have your dub package depend on a prior version.
http://code.dlang.org/packages/stdx-allocator ;)
This is the answer, vibe.d should depend on stdx-allocato
On Tuesday, 6 March 2018 at 12:21:41 UTC, Steven Schveighoffer
wrote:
That being said, I'm wondering if it wouldn't be better to have
std.experimental be in its own repository. This allows
selection of the dependency on std.experimental separate from
phobos. It still would be an "official" dlan
On Monday, 5 March 2018 at 23:40:35 UTC, Atila Neves wrote:
I'd have a snowball's chance in hell convincing anyone at a
"regular" company of adopting D if anyone there even imagined
any of the above could happen.
We have to do better than this.
Atila
I don't think this is unusual even outsi
On Tue, Mar 06, 2018 at 08:50:37PM +, Jack Stouffer via
Digitalmars-d-announce wrote:
[...]
> Also, if you'll allow me to have crazy ideas for a moment, one wonders
> why we shouldn't just release Phobos itself through dub? Rust makes
> people use their build tool, why not us?
Please don't. I
On Tuesday, 6 March 2018 at 20:50:37 UTC, Jack Stouffer wrote:
Also, if you'll allow me to have crazy ideas for a moment, one
wonders why we shouldn't just release Phobos itself through
dub? Rust makes people use their build tool, why not us?
That's the day I stop using D.
I do not, and wil
On 07/03/2018 2:54 PM, psychoticRabbit wrote:
On Tuesday, 6 March 2018 at 20:50:37 UTC, Jack Stouffer wrote:
Also, if you'll allow me to have crazy ideas for a moment, one wonders
why we shouldn't just release Phobos itself through dub? Rust makes
people use their build tool, why not us?
Th
On Tuesday, 6 March 2018 at 19:57:13 UTC, Steven Schveighoffer
wrote:
On 3/6/18 2:30 PM, Martin Nowak wrote:
On Tuesday, 6 March 2018 at 12:21:41 UTC, Steven Schveighoffer
wrote:
But if needed, you could have your dub package depend on a
prior version.
http://code.dlang.org/packages/stdx-al
51 matches
Mail list logo