On Friday, 12 January 2018 at 22:44:48 UTC, Timon Gehr wrote:
As promised [1], I have started setting up a DIP to improve
tuple ergonomics in D:
[...]
Yes please
On Wednesday, 28 February 2018 at 13:43:37 UTC, SimonN wrote:
Hi,
Andrei said in 2014 that not-null-references should be the
priority of 2014's language design, with consideration to make
not-null the default. In case the code breakage is too high,
this can be an opt-in compiler flag.
[...]
On Friday, 11 May 2018 at 18:44:25 UTC, H. S. Teoh wrote:
On Fri, May 11, 2018 at 04:57:05PM +, Mark via
Digitalmars-d wrote:
[...]
This makes me wonder if it might be useful to have return-type
constraints. A kind of static out-contract? Something that's
part of the function declarati
On Thursday, 17 May 2018 at 09:26:34 UTC, rikki cattermole wrote:
On 17/05/2018 8:52 PM, ixid wrote:
On Thursday, 17 May 2018 at 08:51:39 UTC, rikki cattermole
wrote:
On 17/05/2018 8:50 PM, Chris wrote:
For what it's worth, I came across this website:
https://benchmarksgame-team.pages.debian.
On Friday, 18 May 2018 at 12:16:55 UTC, aliak wrote:
You may not need a new word at all. You can also enhance
private to take arguments. Package already does this. You can
give private a symbol list that says which symbols this is
private for. So:
class A {
private int x;
private(A) int
On Friday, 18 May 2018 at 17:59:04 UTC, Dave Jones wrote:
On Friday, 18 May 2018 at 15:40:52 UTC, KingJoffrey wrote:
On Friday, 18 May 2018 at 14:32:33 UTC, bachmeier wrote:
It will attract more programmers, not less - and trust me, D
better get more programmers using it, cause 18 years on,
On Wednesday, 20 June 2018 at 08:16:21 UTC, Mike Parker wrote:
This is the feedback thread for the first round of Community
Review for DIP 1015, "Deprecation and removal of implicit
conversion from integer and character literals to bool":
[...]
Yes please
On Thursday, 28 June 2018 at 00:15:54 UTC, Jonathan M Davis wrote:
On Wednesday, June 27, 2018 16:54:55 Manu via Digitalmars-d
wrote:
Hey people,
So I had a few people in the office refuse to install DMD
because when
they launched the installer, Windows displayed the prompt that
it was
untrus
On Saturday, 30 June 2018 at 15:08:52 UTC, Dmitry Olshansky wrote:
On Saturday, 30 June 2018 at 13:12:44 UTC, Meta wrote:
[...]
Oh my...
I don’t know *exactly* how it works(?)
[...]
I think someone needs to take away your metaphorical keys lol
On Wednesday, 11 July 2018 at 22:59:50 UTC, xray wrote:
The message above is repost of :
https://forum.dlang.org/post/pfjotkcazuiuhlvzi...@forum.dlang.org
So I can reply to Chris M. here.
--
Yes, Chris, I got inspired by Rust :)
On Thursday, 12 July 2018 at 21:31:04 UTC, xray wrote:
On Thursday, 12 July 2018 at 14:13:25 UTC, Chris M. wrote:
On Wednesday, 11 July 2018 at 22:59:50 UTC, xray wrote:
[...]
I feel the following should be disallowed, since we've moved
some checking to runtime. Ideally this system would all
On Friday, 13 July 2018 at 20:03:37 UTC, jmh530 wrote:
On Friday, 13 July 2018 at 17:12:26 UTC, Atila Neves wrote:
[...]
Hmm, thinking on this a little more...it does seem
difficult...but I don't think the problem is with immutable
borrows. I think the issue is with the exclusivity of Rust's
On Tuesday, 24 July 2018 at 16:15:52 UTC, bpr wrote:
On Tuesday, 24 July 2018 at 14:07:43 UTC, Ecstatic Coder wrote:
[...]
No. For many C++ users, tracing GC is absolutely not an option.
And, if it were, D's GC is not a shining example of a good GC.
It's not even precise, and I would bet tha
On Thursday, 23 August 2018 at 15:14:07 UTC, Steven Schveighoffer
wrote:
On 8/23/18 9:32 AM, Steven Schveighoffer wrote:
[...]
Actually, thinking about this, the shortest lifetime is
dictated by how it is called, so there is no valid way to
determine which one makes sense when compiling the
On Thursday, 23 August 2018 at 15:48:00 UTC, Chris M. wrote:
On Thursday, 23 August 2018 at 15:14:07 UTC, Steven
Schveighoffer wrote:
On 8/23/18 9:32 AM, Steven Schveighoffer wrote:
[...]
Actually, thinking about this, the shortest lifetime is
dictated by how it is called, so there is no val
On Thursday, 23 August 2018 at 23:58:00 UTC, jmh530 wrote:
On Thursday, 23 August 2018 at 23:36:07 UTC, Chris M. wrote:
Heck, now that I'm looking at it, DIP25 seems like a more
restricted form of Rust's lifetimes. Let me know if I'm just
completely wrong about this, but
[snip]
Check out D
On Friday, 24 August 2018 at 00:13:48 UTC, Mike Franklin wrote:
On Thursday, 23 August 2018 at 23:36:07 UTC, Chris M. wrote:
Heck, now that I'm looking at it, DIP25 seems like a more
restricted form of Rust's lifetimes. Let me know if I'm just
completely wrong about this, but
I think DIP 25
On Saturday, 25 August 2018 at 02:37:00 UTC, Walter Bright wrote:
On 8/23/2018 5:58 PM, Chris M. wrote:
Seems to be more of a warning of what issues we may face if
DIP25/DIP1000 are finally implemented. It would be good to
consider NLLs as well before D is committed. No point in
repeating issu
Round 2 because I had this whole thing typed up, and then my
power went out on me right before I posted. I was much happier
with how that one was worded too.
Basically I'd like to go over at length one of the issues I see
with these DIPs (though I think it applies more to DIP1000),
namely re
On Tuesday, 4 September 2018 at 16:36:20 UTC, Nick Treleaven
wrote:
Rust's lifetime syntax is noisy - the scope name is repeated,
and why require a name if it's usually not given a meaningful
one (`a`)?
Rust is more limited semantically due to unique mutability, so
it may have different requi
On Sunday, 2 September 2018 at 05:14:58 UTC, Chris M. wrote:
Hopefully that was coherent. Again this is me for me to get my
thoughts out there, but also I'm interested in what other
people think about this.
Somewhat related, I was reading through this thread on why we
can't do ref variables
On Friday, 16 September 2016 at 23:01:32 UTC, eugene wrote:
On Friday, 16 September 2016 at 23:00:08 UTC, eugene wrote:
Hello everyone,
what if to remove semicolons at the end of each line of code
in D like in Python?
Is it worth it?
i.e. simply use a newline sign as a line separator
Point
On Friday, 21 October 2016 at 02:40:45 UTC, Stefan Koch wrote:
On Friday, 21 October 2016 at 02:16:44 UTC, Chris M. wrote:
So I know you can do some pattern matching with templates in
D, but has there been any discussion about implementing it as
a language feature, maybe something similar to Ru
So I know you can do some pattern matching with templates in D,
but has there been any discussion about implementing it as a
language feature, maybe something similar to Rust's match keyword
(https://doc.rust-lang.org/stable/book/patterns.html)? What would
your guys' thoughts be?
On Friday, 21 October 2016 at 19:00:55 UTC, Nick Sabalausky wrote:
On 10/20/2016 10:16 PM, Chris M. wrote:
So I know you can do some pattern matching with templates in
D, but has
there been any discussion about implementing it as a language
feature,
maybe something similar to Rust's match keyw
On Tuesday, 13 December 2016 at 23:03:39 UTC, Timon Gehr wrote:
On 13.12.2016 23:33, Andrei Alexandrescu wrote:
Destroy.
https://github.com/dlang/DIPs/pull/51/files
Andrei
1. The syntax is ambiguous.
Is import.foo.bar.baz the symbol baz in module foo.bar, or the
symbol bar.baz in module f
On Wednesday, 14 December 2016 at 01:39:01 UTC, Andrei
Alexandrescu wrote:
I prefer the current form of the proposal:
bool equal(R1, R2)
import (std.range)
if (isInputRange!R1 && isInputRange!R2)
{ ... }
The point has been brought up that the syntax import(std.range)
is also used for string
On Wednesday, 14 December 2016 at 02:23:07 UTC, Andrei
Alexandrescu wrote:
On 12/13/16 8:53 PM, Chris M. wrote:
On Wednesday, 14 December 2016 at 01:39:01 UTC, Andrei
Alexandrescu wrote:
I prefer the current form of the proposal:
bool equal(R1, R2)
import (std.range)
if (isInputRange!R1 && i
On Wednesday, 14 December 2016 at 22:55:26 UTC, Andrei
Alexandrescu wrote:
Made a pass through the document integrating a lot of feedback
and fleshing the proposal better:
https://github.com/andralex/DIPs/blob/155ff59984b26749af7830aeb172d3af2dae8cd7/DIPs/DIP1005.md
https://github.com/dlang/DI
On Tuesday, 20 December 2016 at 18:01:23 UTC, jmh530 wrote:
It's a fair point, but people only know that all these rants
have come up a million times if they've been following the
newsgroup for a while.
It's the kind of thing where most forums have a read me that
says something like, yes we a
On Tuesday, 20 December 2016 at 19:11:11 UTC, Chris M. wrote:
Seb just made a giant post listing all the things that could be
done to help improve D, that could to be pinned somewhere so
that everyone can see it. Maybe something like that should be
made every time a new high-level vision is mad
On Friday, 13 January 2017 at 21:53:29 UTC, Ignacious wrote:
On Friday, 13 January 2017 at 19:30:40 UTC, Chris Wright wrote:
On Fri, 13 Jan 2017 15:19:57 +, Ignacious wrote:
[...]
LGPL is much more common, and LGPL isn't a problem when you
distribute by source. It *is* a problem with sta
On Tuesday, 14 February 2017 at 03:49:28 UTC, Timothee Cour wrote:
What about allowing syntax sugar as an alternative to relying
on the new `from/Module` inline import idiom:
```
void fun(T)(std.stdio::File input, T value) if
(std.traits::isIntegral!T)
{...}
```
instead of:
```
void fun(T)(
On Friday, 24 February 2017 at 20:16:28 UTC, Timon Gehr wrote:
On 24.02.2017 16:29, Chris Wright wrote:
On Fri, 24 Feb 2017 09:14:24 +0200, ketmar wrote:
forget about "-release" dmd arg. forget about
"-boundscheck=off". no,
really, they won't do you any good. after all, catching a bug
in your
On Sunday, 9 April 2017 at 03:26:14 UTC, Walter Bright wrote:
My previous version did not survive implementation. Here's the
revised version. I have submitted it as a DIP, and there's a
trial implementation up:
[...]
Maybe someone already explained this or the reason is obvious,
but why cou
35 matches
Mail list logo
