On Friday, 29 December 2017 at 22:05:31 UTC, I Love Stuffing
wrote:
Also, for a mature D, some damn collections. Queues, Stacks,
Deques, etc...
std.container.dlist
(https://dlang.org/phobos/std_container_dlist.html)?
On 12/29/2017 7:07 PM, IM wrote:
They start writing
some code, and eventually they hit one of those unhelpful compile error
messages, which could indicate one of the following:
- An error in the engineer's knowledge of the language which the compiler didn't
help to understand what it is so that
Creating a bugzilla account takes a couple minutes. It is enough friction to
serve as a reasonable filter against spammers and junk postings.
It's not like we have a shortage of bugzilla issues and are wondering what to do
next.
It's working well enough for those who care enough to make an ef
On 12/29/2017 5:40 PM, Adam D. Ruppe wrote:
> [...]
PRs to fix bugzilla issues get submitted every day. I don't see a better way. I
can't monitor every forum, I rely on you and others to do so and submit the issues.
On Saturday, 30 December 2017 at 01:34:02 UTC, Mike Franklin
wrote:
On Friday, 29 December 2017 at 21:51:47 UTC, Arun
Chandrasekaran wrote:
All DConf2014 videos have vanished from YouTube.
They are now here:
https://www.youtube.com/channel/UC5DNdmeE-_lS6VhCVydkVvQ
The links on the wiki n
On Friday, 29 December 2017 at 17:29:47 UTC, Adam D. Ruppe wrote:
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
-- Better compiler errors, better compiler errors, better
compiler errors.
This is the only thing I greatly care about anymore. Biggest
problem D has in real world use.
On Saturday, 30 December 2017 at 02:37:24 UTC, IM wrote:
Just curious, why Bugzilla and not something else?
Bugzilla was the most well-known solution at the time. Keep in
mind the D bugzilla has been around since 2006. As far as I
understand it, migration at this point is deemed a big pain.
On Saturday, 30 December 2017 at 01:40:39 UTC, Adam D. Ruppe
wrote:
On Friday, 29 December 2017 at 23:24:45 UTC, Walter Bright
wrote:
That's been closed for a while now.
Well, take your pick:
https://issues.dlang.org/show_bug.cgi?id=12694
https://issues.dlang.org/show_bug.cgi?id=13340
https:/
On Friday, 29 December 2017 at 23:24:45 UTC, Walter Bright wrote:
That's been closed for a while now.
Well, take your pick:
https://issues.dlang.org/show_bug.cgi?id=12694
https://issues.dlang.org/show_bug.cgi?id=13340
https://issues.dlang.org/show_bug.cgi?id=16059
You always tell people to po
On Friday, 29 December 2017 at 21:51:47 UTC, Arun Chandrasekaran
wrote:
All DConf2014 videos have vanished from YouTube.
They are now here:
https://www.youtube.com/channel/UC5DNdmeE-_lS6VhCVydkVvQ
The links on the wiki need to be updated.
Mike
On Fri, Dec 29, 2017 at 05:52:36PM -0700, Jonathan M Davis via Digitalmars-d
wrote:
[...]
> Oh, certainly. But my point is that once it starts taking minutes to
> be able to build and run the unit tests for what you're currently
> doing, it becomes infeasible to edit-test-edit-etc. in any kind of
On Friday, December 29, 2017 15:51:53 H. S. Teoh via Digitalmars-d wrote:
> On Fri, Dec 29, 2017 at 03:49:07PM -0700, Jonathan M Davis via
> Digitalmars-d wrote: [...]
>
> > It also depends on your personality. Personally, while I like builds
> > being near instantaneous when dealing with unit test
On Saturday, 23 December 2017 at 21:04:52 UTC, Laeeth Isharc
wrote:
http://erdani.com/d/downloads.daily.png
Bad data, one off spike, or something else?
https://successfulsoftware.net/2015/05/14/the-mystery-of-the-chinese-downloads/
On Friday, 29 December 2017 at 23:32:45 UTC, Walter Bright wrote:
...
3. Ideally there'd be a url one could click on, not an error
code.
No URLs! (unless they point to 'local' documentation).
I do not want to become even more dependent on having access to
the internet, in order to debu
On Fri, Dec 29, 2017 at 03:49:07PM -0700, Jonathan M Davis via Digitalmars-d
wrote:
[...]
> It also depends on your personality. Personally, while I like builds
> being near instantaneous when dealing with unit tests, if they take a
> few seconds, it's not a big deal, but I know folks who get seri
On 12/29/2017 1:57 PM, rjframe wrote:
I noticed the Rust error has a code, too (E0308); if better error messages
are too difficult to implement, assigning codes to error types and
documenting them on the wiki could be helpful. Once you've dealt with an
error type, the messages aren't that bad, bu
On 12/29/2017 3:15 PM, Muld wrote:
Bugzilla is a huge mess tbh, creating a request in bugzilla won't lead anywhere.
Fixes for bugzilla issues are posted on github nearly every day.
It's so bad honestly it'd probably be less work just to create a new bugzilla
and port any relevant entries fro
On 12/29/2017 2:31 PM, Adam D. Ruppe wrote:
On Friday, 29 December 2017 at 21:30:35 UTC, Walter Bright wrote:
This is not actionable. What is actionable is filing bugzilla enhancement
requests with specific examples.
I've done better than that: I've written pull requests.
https://github.com/d
On Friday, 29 December 2017 at 21:30:35 UTC, Walter Bright wrote:
On 12/29/2017 9:29 AM, Adam D. Ruppe wrote:
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
-- Better compiler errors, better compiler errors, better
compiler errors.
This is the only thing I greatly care about anymo
On Thursday, 28 December 2017 at 21:58:07 UTC, Walter Bright
wrote:
On 12/28/2017 5:22 AM, Atila Neves wrote:
On Thursday, 28 December 2017 at 07:21:28 UTC, Walter Bright
wrote:
On 12/27/2017 1:23 PM, Atila Neves wrote:
However, my experience has been that D has fast builds from
scratch, but i
On Friday, December 29, 2017 22:37:56 I Love Stuffing via Digitalmars-d
wrote:
> To be fair, you are basing this off C++. C++ has an obnoxiously
> slow build system at times and everyone knows this, have known
> this, and have even addressed some parts of it. Yet they still
> use it. I don't think
On Friday, 22 December 2017 at 10:06:18 UTC, Joakim wrote:
This one of the main strengths of D, it is what Walter focuses
on, yet I have seen almost nothing on the D blog talking about
this. What brought me to emphasize this today is this recent
post about how long it takes to compile the most
On Friday, 29 December 2017 at 21:30:35 UTC, Walter Bright wrote:
This is not actionable. What is actionable is filing bugzilla
enhancement requests with specific examples.
I've done better than that: I've written pull requests.
https://github.com/dlang/dmd/pull/6806
There's also existing bug
On Thursday, 28 December 2017 at 13:26:55 UTC, Seb wrote:
On Thursday, 28 December 2017 at 13:20:34 UTC, Atila Neves
wrote:
On Thursday, 28 December 2017 at 07:05:25 UTC, Joakim wrote:
On Sunday, 24 December 2017 at 22:55:12 UTC, aberba wrote:
On Friday, 22 December 2017 at 10:06:18 UTC, Joaki
On Thursday, 28 December 2017 at 15:54:03 UTC, H. S. Teoh wrote:
On Thu, Dec 28, 2017 at 01:22:13PM +, Atila Neves via
Digitalmars-d wrote:
On Thursday, 28 December 2017 at 07:21:28 UTC, Walter Bright
wrote:
> On 12/27/2017 1:23 PM, Atila Neves wrote:
> > However, my experience has been tha
On Friday, 29 December 2017 at 21:56:26 UTC, Seb wrote:
On Friday, 29 December 2017 at 21:34:14 UTC, Walter Bright
wrote:
On 12/28/2017 11:53 PM, IM wrote:
Simple things like these make a big difference. D Lang has
been around for a long while now, and hence signs of its
maturity has to show e
On Friday, 29 December 2017 at 09:46:05 UTC, JN wrote:
AFAIK Rust doesn't have templates, but generics. Generics
usually have much cleaner error messages because they are
mostly used for generic functions and classes, meanwhile
templates can do that too but much, much more, but when they
break
On Fri, 29 Dec 2017 13:34:14 -0800, Walter Bright wrote:
> On 12/28/2017 11:53 PM, IM wrote:
>> Simple things like these make a big difference. D Lang has been around
>> for a long while now, and hence signs of its maturity has to show
>> everywhere, especially in the compiler, as well as the pack
On Friday, 29 December 2017 at 21:34:14 UTC, Walter Bright wrote:
On 12/28/2017 11:53 PM, IM wrote:
Simple things like these make a big difference. D Lang has
been around for a long while now, and hence signs of its
maturity has to show everywhere, especially in the compiler,
as well as the pa
On Thursday, 28 December 2017 at 14:17:56 UTC, Seb wrote:
On Thursday, 28 December 2017 at 14:11:57 UTC, Dave Jones wrote:
Just an idea, i think it'd be a good idea to have a page on
dlang with links to all the various D related talks / videos.
Quite often i watch them as i find them in the new
On 12/28/2017 11:53 PM, IM wrote:
Simple things like these make a big difference. D Lang has been around for a
long while now, and hence signs of its maturity has to show everywhere,
especially in the compiler, as well as the package manager.
Diverging from the:
file(line): message
format
On 12/29/2017 9:29 AM, Adam D. Ruppe wrote:
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
-- Better compiler errors, better compiler errors, better compiler errors.
This is the only thing I greatly care about anymore. Biggest problem D has in
real world use.
This is not actiona
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
-- Better compiler errors, better compiler errors, better
compiler errors.
Very much so.
I actually made a list a day or two ago. Some of it is more
speculative than concrete, though:
* unicode categories to determine what can be an
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
-- Better compiler errors, better compiler errors, better
compiler errors.
This is the only thing I greatly care about anymore. Biggest
problem D has in real world use.
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
I will start:
cut...
Simple things like these make a big difference. D Lang has been
around for a long while now, and hence signs of its maturity
has to show everywhere, especially in the compiler, as well as
the package manager.
I woul
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
I will start:
-- Better compiler errors, better compiler errors, better
compiler errors.
I really wish that the compiler errors could receive some
refinement. Mostly it feels like some error text just being
thrown at me. It needs to
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
I will start:
[...]
Simple things like these make a big difference. D Lang has been
around for a long while now, and hence signs of its maturity
has to show everywhere, especially in the compiler, as well as
the package manager.
I casual
On 29/12/2017 11:03 AM, maarten van damme wrote:
>I'd like to see proper DLL (shared library) support and DIP45
implemented. I'm making a project that I hope in the future will be
extendable with D plugins.
Out of curiousity, what's wrong with the current dll support?
The starting problem
>I'd like to see proper DLL (shared library) support and DIP45 implemented.
I'm making a project that I hope in the future will be extendable with D
plugins.
Out of curiousity, what's wrong with the current dll support?
2017-12-29 11:36 GMT+01:00 angel via Digitalmars-d <
digitalmars-d@puremagic
Built-in tuples:
{val1, val2} = func();
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
I will start:
-- Better compiler errors, better compiler errors, better
compiler errors.
I really wish that the compiler errors could receive some
refinement. Mostly it feels like some error
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
I will start:
-- Better compiler errors, better compiler errors, better
compiler errors.
I really wish that the compiler errors could receive some
refinement. Mostly it feels like some error text just being
thrown at me. It needs to
AFAIK Rust doesn't have templates, but generics. Generics usually
have much cleaner error messages because they are mostly used for
generic functions and classes, meanwhile templates can do that
too but much, much more, but when they break, you get entire
paragraphs of template errors.
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
I will start:
-- Better compiler errors, better compiler errors, better
compiler errors.
I really wish that the compiler errors could receive some
refinement. Mostly it feels like some error text just being
thrown at me. It needs to
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
I will start:
I will add:
// --
module test;
import std.stdio;
@safe void main()
{
writeln("I'd like to see @safe as being the default");
}
//
On Friday, 29 December 2017 at 08:02:36 UTC, IM wrote:
On Friday, 29 December 2017 at 07:55:08 UTC, Daniel Kozak wrote:
But maybe you can propose cjange from ref R r to auto ref R r
If this will make it work with both lvalues and rvalues, then
yes, this would be a nice fix. No need to force
On Friday, 29 December 2017 at 07:54:53 UTC, Mengu wrote:
On Friday, 29 December 2017 at 00:26:04 UTC, codephantom wrote:
On Thursday, 28 December 2017 at 08:53:25 UTC, Russel Winder
wrote:
[...]
I disagree.
[...]
syntax is not weird at all. it is ML-ish.
oh. I didn't know..
in any case
On 12/28/2017 2:16 PM, Iain Buclaw wrote:
D modules are like C++ headers. Change one, and you need to recompile
everything that imports it.
That's right. That doesn't mean that D should incrementally compile slower than
C++.
On Friday, 29 December 2017 at 07:55:08 UTC, Daniel Kozak wrote:
But maybe you can propose cjange from ref R r to auto ref R r
If this will make it work with both lvalues and rvalues, then
yes, this would be a nice fix. No need to force users to cache
string line = readln(); first and then u
You should fill an issue on issues.dlang.org for this particular case.
Compile should give you some hint, that you should use lvalue instead of
rvalue.
On Fri, Dec 29, 2017 at 8:53 AM, IM via Digitalmars-d <
digitalmars-d@puremagic.com> wrote:
> I will start:
>
>-- Better compiler errors, bet
49 matches
Mail list logo
