Which tools do you miss in the D language? it can be from any
language not from C or C++ only but from any language that you
have used and liked (might not liked but increased productivity
anyway)  A very common argument from peoples which do choose
other language than D is lack of your tools for D, even if they
want to get D they say can't switch. The most common tools which
they miss is debuggers/static analyzer/lint and so on. I think
that by sharing this list with community instead of just say it
like a criticizes is good because next time that some people say
that such a x tools isn't available you can say "No, there's a D
version for that". Also, totally new ideas are very welcome. If
you  have had a idea that for any reason you wouldn't implement
yourself, tell us too.
(sorry for english, not my native language)

On Sunday, 26 January 2014 at 20:29:30 UTC, Oten wrote:
> Which tools do you miss in the D language? it can be from any
> language not from C or C++ only but from any language that you
> have used and liked (might not liked but increased productivity
> anyway)  A very common argument from peoples which do choose
> other language than D is lack of your tools for D, even if they
> want to get D they say can't switch. The most common tools which
> they miss is debuggers/static analyzer/lint and so on. I think
> that by sharing this list with community instead of just say it
> like a criticizes is good because next time that some people say
> that such a x tools isn't available you can say "No, there's a D
> version for that". Also, totally new ideas are very welcome. If
> you  have had a idea that for any reason you wouldn't implement
> yourself, tell us too.
> (sorry for english, not my native language)

Detection of unused imports and variables!

On Sunday, 26 January 2014 at 20:29:30 UTC, Oten wrote:
> Which tools do you miss in the D language? it can be from any
> language not from C or C++ only but from any language that you
> have used and liked (might not liked but increased productivity
> anyway)  A very common argument from peoples which do choose
> other language than D is lack of your tools for D, even if they
> want to get D they say can't switch. The most common tools which
> they miss is debuggers/static analyzer/lint and so on. I think
> that by sharing this list with community instead of just say it
> like a criticizes is good because next time that some people say
> that such a x tools isn't available you can say "No, there's a D
> version for that". Also, totally new ideas are very welcome. If
> you  have had a idea that for any reason you wouldn't implement
> yourself, tell us too.
> (sorry for english, not my native language)

Code formatter
import management tool (able to detect unused imports, duplicated, etc . . .)
Refactoring tool (change the name of something, signature, etc . . .)
REPL, so I can do some quick experiments.

On Sunday, 26 January 2014 at 20:29:30 UTC, Oten wrote:
> Which tools do you miss in the D language? it can be from any
> language not from C or C++ only but from any language that you
> have used and liked (might not liked but increased productivity
> anyway)  A very common argument from peoples which do choose
> other language than D is lack of your tools for D, even if they
> want to get D they say can't switch. The most common tools which
> they miss is debuggers/static analyzer/lint and so on. I think
> that by sharing this list with community instead of just say it
> like a criticizes is good because next time that some people say
> that such a x tools isn't available you can say "No, there's a D
> version for that". Also, totally new ideas are very welcome. If
> you  have had a idea that for any reason you wouldn't implement
> yourself, tell us too.
> (sorry for english, not my native language)

I'm not missing any tool.
For me the lack of std.logger and std.allocator very annoying though. This makes each library resemble to an island.

A D backend for iPython would be cool. But first D needs a "pseudo-repl" using rdmd. It might be feasible with the ØMQD just announced (communication to the iPython frontend is done through ØMQ).

On libraries I really miss the Collections library, since sometimes I like to participate on programming competitions and a direct standard containers library would be great for that. But Allocators are - theoretically - blocking a Collections library ; - ;.

On Sunday, 26 January 2014 at 22:35:20 UTC, Alessandro Stamatto wrote:
> On libraries I really miss the Collections library, since sometimes I like to participate on programming competitions and a direct standard containers library would be great for that. But Allocators are - theoretically - blocking a Collections library ; - ;.

There are standard collections in std.container, but indeed the impending allocator design has been holding back further development of the module.

On Sunday, 26 January 2014 at 20:29:30 UTC, Oten wrote:
> Which tools do you miss in the D language? it can be from any
> language not from C or C++ only but from any language that you
> have used and liked (might not liked but increased productivity
> anyway)  A very common argument from peoples which do choose
> other language than D is lack of your tools for D, even if they
> want to get D they say can't switch. The most common tools which
> they miss is debuggers/static analyzer/lint and so on. I think
> that by sharing this list with community instead of just say it
> like a criticizes is good because next time that some people say
> that such a x tools isn't available you can say "No, there's a D
> version for that". Also, totally new ideas are very welcome. If
> you  have had a idea that for any reason you wouldn't implement
> yourself, tell us too.
> (sorry for english, not my native language)

A quality GUI api with a decent GUI builder, something like the tools that come with Qt or that Window Builder for Java.

I find GTKD bindings are great but the GTK api itself, IMO, is less intuitive than Qt and GTK+Glade is a lot more work compared to other RAD tools in C++ or Java.


Cheers,
Ed

I miss check_expect from racket.

It is used for unit testing

check_expect(expression, result)
Will test if expression equals result
if it is not it print "Got expression but expected result" with file and
line information.

In D making unit tests is more tedious.
When I develop in D I typical start with.

writeln(expression)
writeln(result)

then when the code is working I replace it with
assert(expression==result)

Then if I do some refactoring which don't work I change again
writeln(expression)
writeln(result)

When it is working again
assert(expression==result)

This back and forth process in D is very tedious compared to Racket.

I think the should be a buildin function called test or something for-filing the same role as check_expect in racket.

Knud

On 2014-01-26 21:29, Oten wrote:
> Which tools do you miss in the D language? it can be from any
> language not from C or C++ only but from any language that you
> have used and liked (might not liked but increased productivity
> anyway)  A very common argument from peoples which do choose
> other language than D is lack of your tools for D, even if they
> want to get D they say can't switch. The most common tools which
> they miss is debuggers/static analyzer/lint and so on. I think
> that by sharing this list with community instead of just say it
> like a criticizes is good because next time that some people say
> that such a x tools isn't available you can say "No, there's a D
> version for that". Also, totally new ideas are very welcome. If
> you  have had a idea that for any reason you wouldn't implement
> yourself, tell us too.
> (sorry for english, not my native language)


-- 
Join me on
Skype	   knudhs
Facebook   http://www.facebook.com/profile.php?id=1198821880
Linkedin   http://www.linkedin.com/pub/0/117/a54
Twitter    http://twitter.com/knudsoerensen
bitcoin donations: 13ofyUKqFL43uRJHZtNozyMVP4qxKPsAR2

In order:

1. A debugger (that works properly)
2. Go-to definition (that always works)
3. Auto-complete (that always works)
4. Import management (missing/duplicate/unused imports)
5. Typical suite of modern refactoring tools

On 27 January 2014 18:11, Manu <turkeyman@gmail.com> wrote:

> In order:
>
> 1. A debugger (that works properly)
> 2. Go-to definition (that always works)
> 3. Auto-complete (that always works)
> 4. Import management (missing/duplicate/unused imports)
> 5. Typical suite of modern refactoring tools
>

I might add, the frequency to which I pine for these things is in the order of minutes, perhaps even 10s of seconds >_<

I made an interesting observation recently... D has kind of ruined my
career ;)
Before I started using D a lot, I found C/C++ quite okay as a language. But
after extended time using D, I find C/C++ borderline intolerable, and don't
enjoy writing it at all.
But the tooling built around C/C++ is pretty good, and as such, I find the
tooling while working in D borderline intolerable.

So, before, I generally enjoyed my work, and felt generally productive. Now days, whenever I do any work in either language, I find one aspect or the other borderline intolerable, and I have trouble enjoying spending my time programming for long periods before getting frustrated and going and doing something else...

I'm quite serious, this is a true realisation of an unconscious behaviour. D ruined C/C++ for me, but my expectations of C/C++'s tooling still remains a barrier to my enjoyment of writing D code all time time... I'm fucked!