Hey all,
there are a lot of complaints recently and if one looks at the
high-level vision document (https://wiki.dlang.org/Vision/2016H2)
there are many projects one can start to change the status quo.
However, as most of them might require a lot of time or
expertise, here are a couple of id
Ilya Yaroshenko wrote:
> This is small but pleasant proof that D can be a backend language
> for high performance software. Go and Rust developers will be
> happy to use D under the hood of Go/Rust API if we can propose
> the best libraries. They do not against D! The only things we
> need to
On Tuesday, 20 December 2016 at 04:38:03 UTC, Jerry wrote:
On Tuesday, 20 December 2016 at 04:14:33 UTC, Andrei
Alexandrescu wrote:
On 12/19/2016 11:12 PM, Andrei Alexandrescu wrote:
[...]
https://issues.dlang.org/show_bug.cgi?id=16991
Another issue onto the list of thousands, to collect du
what about using `lazy` instead of `with`:
`with(import foo)`
=>
`lazy(import foo)`
advantages:
* avoids confusion regarding usual scoping rules of `with` ;
* conveys that the import is indeed lazy
Furthermore (regardless of which keyword is used), what about allowing `:`
```
// case 1
lazy(impo
Andrei: you can use blockquotes to make long lines wrap when quoting text:
https://github.com/adam-p/markdown-here/wiki/Markdown-Here-Cheatsheet#blockquotes
that way, we don't have to scroll everytime there's a quote, eg:
replace:
Such scaffolding is of course
with:
> Such scaffolding is of cour
On Tuesday, 20 December 2016 at 04:14:33 UTC, Andrei Alexandrescu
wrote:
On 12/19/2016 11:12 PM, Andrei Alexandrescu wrote:
On 12/19/2016 10:56 PM, Suliman wrote:
The whole focus on C++ people marketing is simply wrong!
Every time
this gets mentioned in external forums, the language gets a
pou
On 12/19/2016 11:12 PM, Andrei Alexandrescu wrote:
On 12/19/2016 10:56 PM, Suliman wrote:
The whole focus on C++ people marketing is simply wrong! Every time
this gets mentioned in external forums, the language gets a pounding
by people with the same argumentation. Why go for D when C++ 20xx
ver
On 12/19/2016 10:56 PM, Suliman wrote:
The whole focus on C++ people marketing is simply wrong! Every time
this gets mentioned in external forums, the language gets a pounding
by people with the same argumentation. Why go for D when C++ 20xx
version does it also.
+100
I totally agree with anot
On 12/19/2016 01:47 AM, Joakim wrote:
Why do you care _so_ much about the module dependency graph? To make
this question concrete, let's look at an example, the std.array module
you keep mentioning.
This is what it looked like before Ilya scoped as
many imports as he could:
https://github.com/d
The whole focus on C++ people marketing is simply wrong! Every
time this gets mentioned in external forums, the language gets a
pounding by people with the same argumentation. Why go for D
when C++ 20xx version does it also.
+100
I totally agree with another part of post. Plus the docs is
re
On 12/17/2016 10:39 AM, Jacob Carlborg wrote:
On 2016-12-13 23:33, Andrei Alexandrescu wrote:
Destroy.
https://github.com/dlang/DIPs/pull/51/files
A couple of questions.
1. The text says:
"void process(File input) import (std.stdio);
With this syntax, the import is executed only if the dec
On 12/15/2016 02:23 AM, Dominikus Dittes Scherkl wrote:
Also I hate prototypes: .di-files are pretty useless - they make not
clear what is needed to include and for templates you need the whole
code anyway.
BTW are there outstanding issues with .di files? I recall some solid
improvements were
On 12/14/2016 08:59 PM, Timothee Cour via Digitalmars-d wrote:
how about this:
variant 1 // currently legal D; just need to attach semantics
```
// applies to all below
@deps!({import std.stdio; pragma(lib, "curl"); }):
Thanks, added. -- Andrei
On 12/14/2016 06:17 PM, Andrej Mitrovic wrote:
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/155ff59984b26749af7830aeb172d3af2dae8c
On 12/14/2016 06:11 PM, H. S. Teoh via Digitalmars-d wrote:
On thinking about this again, though, isn't the whole point of this DIP
to add a way of attaching imports X, Y, Z to some declaration such that
the imports are in effect for the scope of the declaration? The
specific syntax is really se
Added this note about module constructors:
## Future Possibilities and Directions
Inline and scoped imports offer the option of better handling of static
module constructors. Currently, modules that mutually `import` one
another (either directly or through a longer chain) cannot
simultaneousl
On 12/19/2016 06:19 PM, Adam D. Ruppe wrote:
On Monday, 19 December 2016 at 23:02:59 UTC, Benjiro wrote:
Vim: Lets not go there.
Why not? If you already know vim at least, it is very easy to use with D
- things just work quite well out of the box.
Try remote editing D and see how much fun it
On Monday, 19 December 2016 at 23:02:59 UTC, Benjiro wrote:
Vim: Lets not go there.
Why not? If you already know vim at least, it is very easy to use
with D - things just work quite well out of the box.
Try remote editing D and see how much fun it is.
works in vim out of the box...
On Tuesday, 20 December 2016 at 01:45:27 UTC, Tommi wrote:
Half of the paragraphs contradict the other half. Walter must
headbutt himself in the face reading this.
You may want to try to understand all paragraphs together as a
solid text.
I see a lot of people arguing a lot about D and sorry to say
but at times it sounds like a kindergarten. Walter/Andrei are
right that updates and changes need to be focused on the
standard library.
Improve the standard library!
Some of the proposals sounds very correct. The library needs to
Pushed again, now with the syntax using "with" proposed by Hatem Oraby
and others.
https://github.com/dlang/DIPs/pull/51
https://github.com/dlang/DIPs/blob/71bde077488b566fba7603de6095b45984d9294a/DIPs/DIP1005.md
Andrei
On Monday, 19 December 2016 at 23:03:47 UTC, Mark wrote:
On Monday, 19 December 2016 at 18:38:32 UTC, Ilya Yaroshenko
wrote:
Mir can be translated as "Peace". Cooperation with other
languages through betterC API is more productive than
universality/feature wars :-)
And here I thought it was n
On Monday, 19 December 2016 at 18:38:32 UTC, Ilya Yaroshenko
wrote:
Mir can be translated as "Peace". Cooperation with other
languages through betterC API is more productive than
universality/feature wars :-)
And here I thought it was named after the space station. =)
I split this from the "Re: A betterC modular standard library?"
topic because my response is will be too much off-topic but the
whole thread is irking me the wrong way. I see some of the same
argument coming up all the time, with a level of frequency.
D has not market:
-
A lot
On Monday, 19 December 2016 at 11:26:26 UTC, keito940 wrote:
Hello. I'm Japanese D Language User. I am not good at English.
I want to get into the main subject though it is quickly.
Visual D,D Language Visual D IDE to Good Idea.
...But English Only.Could you cope with Japanese or somehow?
I can
On Monday, 19 December 2016 at 21:00:57 UTC, lurker wrote:
On Monday, 19 December 2016 at 05:59:07 UTC, Ilya Yaroshenko
wrote:
[...]
Thats why I asked for moderation in forums.
+1, and ability to edit own posts.
On Monday, 19 December 2016 at 05:59:07 UTC, Ilya Yaroshenko
wrote:
On Monday, 19 December 2016 at 01:52:21 UTC, Andrei
Alexandrescu wrote:
On 12/18/16 7:31 PM, Seb wrote:
tl:dr: Phobos is very bloated.
How does the D standard library compare in size with some
other languages (C++, Rust, Go,
On Monday, 19 December 2016 at 20:10:02 UTC, Ilya Yaroshenko
wrote:
On Monday, 19 December 2016 at 19:59:01 UTC, Guillaume Piolat
wrote:
On Monday, 19 December 2016 at 19:54:54 UTC, Ilya Yaroshenko
wrote:
To be more precise: I do not build library exclusively for D.
They should be easily inte
On Monday, 19 December 2016 at 20:24:21 UTC, Guillaume Piolat
wrote:
On Monday, 19 December 2016 at 20:05:20 UTC, Ilya Yaroshenko
wrote:
[...]
If Mir libs are static libs this can indeed be a problem.
If someone has made another D library like this, it will either
have to be its own dynlib or
On 19 December 2016 at 21:29, Ilya Yaroshenko via Digitalmars-d
wrote:
> On Monday, 19 December 2016 at 20:22:29 UTC, Iain Buclaw wrote:
>>
>> On 19 December 2016 at 20:42, Ilya Yaroshenko via Digitalmars-d
>> wrote:
>>>
>>> On Monday, 19 December 2016 at 19:31:24 UTC, Guillaume Piolat wrote:
>>>
On Monday, 19 December 2016 at 20:22:29 UTC, Iain Buclaw wrote:
On 19 December 2016 at 20:42, Ilya Yaroshenko via Digitalmars-d
wrote:
On Monday, 19 December 2016 at 19:31:24 UTC, Guillaume Piolat
wrote:
On Sunday, 18 December 2016 at 09:26:09 UTC, Ilya Yaroshenko
wrote:
[...]
If I unde
On 19 December 2016 at 20:42, Ilya Yaroshenko via Digitalmars-d
wrote:
> On Monday, 19 December 2016 at 19:31:24 UTC, Guillaume Piolat wrote:
>>
>> On Sunday, 18 December 2016 at 09:26:09 UTC, Ilya Yaroshenko wrote:
>>>
>>> [...]
>>
>>
>> If I understand correctly, the only reaon not to disable th
On Monday, 19 December 2016 at 20:05:20 UTC, Ilya Yaroshenko
wrote:
What about other non Mir numerical library written in Dlang,
say for FFT?
How they should be linked together.
If Mir libs are static libs this can indeed be a problem.
If someone has made another D library like this, it will
On Monday, 19 December 2016 at 19:59:01 UTC, Guillaume Piolat
wrote:
On Monday, 19 December 2016 at 19:54:54 UTC, Ilya Yaroshenko
wrote:
To be more precise: I do not build library exclusively for D.
They should be easily interacted with other languages.
Non sequitur, you can enable the runti
On Monday, 19 December 2016 at 19:57:45 UTC, Guillaume Piolat
wrote:
On Monday, 19 December 2016 at 19:52:43 UTC, Ilya Yaroshenko
wrote:
How this can work for libraries? Please read this thread.
This is not realistic. This a huge constraint for D libraries
to be modular, replaceable and distrib
On Monday, 19 December 2016 at 19:54:54 UTC, Ilya Yaroshenko
wrote:
To be more precise: I do not build library exclusively for D.
They should be easily interacted with other languages.
Non sequitur, you can enable the runtime/attah threads withing
callbacks.
On Monday, 19 December 2016 at 19:52:43 UTC, Ilya Yaroshenko
wrote:
How this can work for libraries? Please read this thread.
This is not realistic. This a huge constraint for D libraries
to be modular, replaceable and distributed in binary form.
They can be at the MIR level.
How this can wor
On Monday, 19 December 2016 at 18:41:36 UTC, Ilya Yaroshenko
wrote:
On Monday, 19 December 2016 at 18:38:32 UTC, Ilya Yaroshenko
wrote:
In my Christmas, say for 2050 year...
i wish D to be a default language for multi-language
interaction.
extern(Rust)?
extern(Go)?
;)
Johan
On Monday, 19 December 2016 at 19:52:43 UTC, Ilya Yaroshenko
wrote:
On Monday, 19 December 2016 at 19:48:39 UTC, Guillaume Piolat
wrote:
On Monday, 19 December 2016 at 19:42:42 UTC, Ilya Yaroshenko
wrote:
No,
1. DRuntime has not fixed API
Can't you static link with it? If you static link with
On Monday, 19 December 2016 at 19:48:39 UTC, Guillaume Piolat
wrote:
On Monday, 19 December 2016 at 19:42:42 UTC, Ilya Yaroshenko
wrote:
No,
1. DRuntime has not fixed API
Can't you static link with it? If you static link with it, your
client don't deal with DRuntime.
2. It has not backwar
On Monday, 19 December 2016 at 19:42:42 UTC, Ilya Yaroshenko
wrote:
No,
1. DRuntime has not fixed API
Can't you static link with it? If you static link with it, your
client don't deal with DRuntime.
2. It has not backward binary compatibility
Ditto. If you static link with it, your clien
On Monday, 19 December 2016 at 19:31:24 UTC, Guillaume Piolat
wrote:
On Sunday, 18 December 2016 at 09:26:09 UTC, Ilya Yaroshenko
wrote:
[...]
If I understand correctly, the only reaon not to disable the
runtime instead of going betterC (what I call runtime-free vs
runtime-less) is because P
On Sunday, 18 December 2016 at 09:26:09 UTC, Ilya Yaroshenko
wrote:
Hi,
Who is interested in betterC _modular_* standard library?
I am planing to make libmir org a community for it.
Thought and concerns?
We already have better `cpuid` and better `random` packages.
The betterC std.range and std
On Monday, 19 December 2016 at 18:38:32 UTC, Ilya Yaroshenko
wrote:
In my Christmas, say for 2050 year...
i wish D to be a default language for multi-language interaction.
https://news.ycombinator.com/item?id=13209861
Mir GLAS [1] raised 11 stars and 138 views during 11 hours
because someone noted it in the discussion.
Interesting note: 4 stars was from Go and Rust developers.
This is small but pleasant proof that D can be a backend language
for high performanc
On 12/19/16 12:25 PM, Atila Neves wrote:
On Monday, 19 December 2016 at 17:11:38 UTC, Adam D. Ruppe wrote:
On Monday, 19 December 2016 at 17:04:43 UTC, Atila Neves wrote:
Nope, no magic. Just ModuleInfo.opApply in object.d.
Well, it is kinda magical because combining all the ModuleInfo takes
On 12/19/16 1:25 PM, Basile B. wrote:
On Sunday, 18 December 2016 at 16:53:24 UTC, Andrei Alexandrescu wrote:
Compulsive ModuleInfo generation seems to be a drag. I'm not very
familiar with the particulars but my understanding is ModuleInfo is
needed for (a) Object.factory and (b) finding and ru
On Sunday, 18 December 2016 at 16:53:24 UTC, Andrei Alexandrescu
wrote:
Compulsive ModuleInfo generation seems to be a drag. I'm not
very familiar with the particulars but my understanding is
ModuleInfo is needed for (a) Object.factory and (b) finding and
running unittests.
Walter and I think
On Monday, 19 December 2016 at 18:04:14 UTC, safety0ff wrote:
On Sunday, 18 December 2016 at 18:02:58 UTC, Ilya Yaroshenko
wrote:
Thank you for the answer (it is hard to understand me because
English and other reasons),
Ilya
It was difficult to understand your vision until this post, now
On Sunday, 18 December 2016 at 18:02:58 UTC, Ilya Yaroshenko
wrote:
Thank you for the answer (it is hard to understand me because
English and other reasons),
Ilya
It was difficult to understand your vision until this post, now I
think I grasp it.
Let me try to summarize what I've underst
On Monday, 19 December 2016 at 17:11:38 UTC, Adam D. Ruppe wrote:
On Monday, 19 December 2016 at 17:04:43 UTC, Atila Neves wrote:
Nope, no magic. Just ModuleInfo.opApply in object.d.
Well, it is kinda magical because combining all the ModuleInfo
takes some tricks from the linker. This method
On Monday, 19 December 2016 at 17:04:43 UTC, Atila Neves wrote:
Nope, no magic. Just ModuleInfo.opApply in object.d.
Well, it is kinda magical because combining all the ModuleInfo
takes some tricks from the linker. This method works with
separate compilation, whereas the compile time tricks d
On Monday, 19 December 2016 at 00:15:24 UTC, Nicholas Wilson
wrote:
On Monday, 19 December 2016 at 00:00:36 UTC, Andrei
Alexandrescu wrote:
On 12/18/16 6:48 PM, Nicholas Wilson wrote:
[...]
Cool cool cool. Thanks.
[...]
Noice. Wait, the top foreach iterates what?
Its a compile
On Monday, 19 December 2016 at 00:00:36 UTC, Andrei Alexandrescu
wrote:
On 12/18/16 6:48 PM, Nicholas Wilson wrote:
On Sunday, 18 December 2016 at 16:53:24 UTC, Andrei
Alexandrescu wrote:
[...]
Don't forget that typeinfos are classes too, which makes the
class
attribute approach less attrac
On Sunday, 18 December 2016 at 16:53:24 UTC, Andrei Alexandrescu
wrote:
Compulsive ModuleInfo generation seems to be a drag. I'm not
very familiar with the particulars but my understanding is
ModuleInfo is needed for (a) Object.factory and (b) finding and
running unittests.
Walter and I think
On Sunday, 18 December 2016 at 16:53:24 UTC, Andrei Alexandrescu
wrote:
What other issues/opportunities do you see related to
ModuleInfo?
IIRC TypeInfo is generated for C++ classes.
On Monday, 19 December 2016 at 12:36:13 UTC, Sönke Ludwig wrote:
Am 19.12.2016 um 11:24 schrieb biocyberman:
Hi
I am learning D and dub, and playing with this repository:
https://github.com/biod/BioD
The whole repo itself and be compiled with `dub build`
command. How
write dub.json under `examp
On Sunday, December 18, 2016 18:29:16 Timothee Cour via Digitalmars-d wrote:
> I keep running into issues due to auto-decoding (arguably a significant
> design flaw of phobos) when using strings from external sources (which may
> not be 100% valid UTF8) eg see stracktrace [1] on
> getSomeExternalSt
Am 19.12.2016 um 11:24 schrieb biocyberman:
Hi
I am learning D and dub, and playing with this repository:
https://github.com/biod/BioD
The whole repo itself and be compiled with `dub build` command. How
write dub.json under `examples` directory and compile every d source
file in there?
The clea
On 2016-12-18 14:38, Andrei Alexandrescu wrote:
How does the lack of the feature save lines? Doesn't it just move them
elsewhere?
Yes, I was referring to the file containing the implementation.
Does that include full documentation and unittests?
It does not count the documentation in those
On Monday, 19 December 2016 at 10:24:08 UTC, Basile B. wrote:
On Monday, 19 December 2016 at 08:30:07 UTC, Stefan Koch wrote:
If you are prepending # you might as well prepend _
No, because # is not an identifier char while _ is.
* _delegate is 1 token (_delegate)
* #delegate is 2 tokens ( #
Hello. I'm Japanese D Language User. I am not good at English.
I want to get into the main subject though it is quickly.
Visual D,D Language Visual D IDE to Good Idea.
...But English Only.Could you cope with Japanese or somehow?
On Monday, 19 December 2016 at 10:11:18 UTC, Nordlöw wrote:
On Monday, 19 December 2016 at 08:26:00 UTC, Stefan Koch wrote:
Soon newCTFE will compile Phobos without any blacklisted
functions!
Which functions are still blacklisted?
Check here
https://github.com/UplinkCoder/dmd/blob/newCTFE/sr
On Monday, 19 December 2016 at 09:58:28 UTC, default0 wrote:
On Monday, 19 December 2016 at 08:30:07 UTC, Stefan Koch wrote:
On Monday, 19 December 2016 at 08:14:44 UTC, Basile B. wrote:
I know that there is other hot stuffs since a few days but
this is a really simple DIP, that has no effect o
Hi
I am learning D and dub, and playing with this repository:
https://github.com/biod/BioD
The whole repo itself and be compiled with `dub build` command.
How write dub.json under `examples` directory and compile every d
source file in there?
On Monday, 19 December 2016 at 08:30:07 UTC, Stefan Koch wrote:
On Monday, 19 December 2016 at 08:14:44 UTC, Basile B. wrote:
I know that there is other hot stuffs since a few days but
this is a really simple DIP, that has no effect on the grammar
and no effect on the semantic. It was drafted a
On Monday, 19 December 2016 at 08:26:00 UTC, Stefan Koch wrote:
Soon newCTFE will compile Phobos without any blacklisted
functions!
Which functions are still blacklisted?
On Monday, 19 December 2016 at 05:59:07 UTC, Ilya Yaroshenko
wrote:
D - ??? awesome what ? What do we have better then Scala?
Performance? NO.
BRandomAccessRanges makes our performance less then C/C++.
Clean and clever API in standard library? NO.
We are placing our Range API whenever possible
On 18/12/16 22:24, Andrei Alexandrescu wrote:
IIRC there is an option in gmake that allows one to run all commands
within the same shell.
https://www.gnu.org/software/make/manual/html_node/One-Shell.html.
Was not aware of this. Thanks!
Too bad it's an all or nothing thing. It would, otherwise,
On Monday, 19 December 2016 at 08:30:07 UTC, Stefan Koch wrote:
On Monday, 19 December 2016 at 08:14:44 UTC, Basile B. wrote:
I know that there is other hot stuffs since a few days but
this is a really simple DIP, that has no effect on the grammar
and no effect on the semantic. It was drafted a
On Monday, 19 December 2016 at 08:26:00 UTC, Stefan Koch wrote:
Soon newCTFE will compile Phobos without any blacklisted
functions!
Awesome!
On Sunday, 18 December 2016 at 22:50:36 UTC, Brad Anderson wrote:
On Sunday, 18 December 2016 at 21:29:05 UTC, jmh530 wrote:
On Sunday, 18 December 2016 at 21:26:36 UTC, Boston wrote:
Some days ago I'd been looking for comparisons between
different programming languages, and I found this site:
On Monday, 19 December 2016 at 08:26:00 UTC, Stefan Koch wrote:
On Saturday, 17 December 2016 at 09:39:02 UTC, Stefan Koch
wrote:
On Saturday, 17 December 2016 at 08:53:07 UTC, Stefan Koch
wrote:
Miscompiling phobos code is down to 4 functions.
std.range.primitives.{front, empty, back}
and std.
On Monday, 19 December 2016 at 08:14:44 UTC, Basile B. wrote:
I know that there is other hot stuffs since a few days but this
is a really simple DIP, that has no effect on the grammar and
no effect on the semantic. It was drafted after the announce of
DIP 1003 last week. During a discussion I'v
On Saturday, 17 December 2016 at 09:39:02 UTC, Stefan Koch wrote:
On Saturday, 17 December 2016 at 08:53:07 UTC, Stefan Koch
wrote:
Miscompiling phobos code is down to 4 functions.
std.range.primitives.{front, empty, back}
and std.traits.defaultParameters.
Note, StructLiterals are still regresse
I know that there is other hot stuffs since a few days but this
is a really simple DIP, that has no effect on the grammar and no
effect on the semantic. It was drafted after the announce of DIP
1003 last week. During a discussion I've proposed to take a
radically different approach. This approa
76 matches
Mail list logo