"Andrei Alexandrescu" wrote in message
news:mgcqml$2e67$1...@digitalmars.com...
This is nice work, but sorry it is hardly conductive to warm fuzzy
feelings. -- Andrei
It's not ideal, just better than what we have now.
On 4/11/15 5:35 AM, matovitch wrote:
I am not convinced by the dip77, what about raii managed classes with
costly opAssign operator (like in w0rn example) ? The goal of passing an
object by reference is to avoid the copy and here you guess the
parameter is ref-counted and made a (pseudo-)copy ? T
On 4/11/15 4:03 AM, w0rp wrote:
Having thought about it more, I think that is why we cannot put the
range primitives for slices into object.d. Because that makes it
impossible to define the primitives differently, so that no
auto-decoding occurs. At the moment, auto-decoding isn't part of the
lan
On 4/11/15 12:25 AM, Vladimir Panteleev wrote:
On Friday, 10 April 2015 at 23:04:44 UTC, Andrei Alexandrescu wrote:
Martin Nowak added recently a nice feature to the Phobos makefile: by
specifying e.g.
make std/stdio.test
only the unittests for std/stdio.d would build and run. This greatly
imp
On 4/10/15 8:45 PM, Daniel Murphy wrote:
"Andrei Alexandrescu" wrote in message
news:mg94od$1v4g$1...@digitalmars.com...
Can you make a salient argument that this is a step in the right
direction? In that case what's the vision for future steps? Thanks! --
Andrei
This approach makes the comm
Thanks for the feedback, I think I've incorporated all the
suggested changes.
Also added a section on how D deals with object slicing.
I can't seem to get the compiler to error on dangling else. I
tried the examples in the original PR[1], but they seem to
compile without error with DMD 2.067.
On Saturday, 11 April 2015 at 16:02:53 UTC, David Nadlinger wrote:
On Saturday, 11 April 2015 at 10:24:53 UTC, Jakob Ovrum wrote:
http://wiki.dlang.org/Coming_From/C_Plus_Plus_WIP_article
*Un*signed integer overflow isn't undefined in C/C++ either.
— David
I removed the section on undefine
On Sunday, 12 April 2015 at 01:45:16 UTC, Martin Nowak wrote:
On 04/12/2015 12:35 AM, weaselcat wrote:
How does this differ from e.g, if the function was templated?
It doesn't, if you decide to analyze each imported function to
perform
attribute inference, then that's just like treating all o
On Saturday, 11 April 2015 at 17:14:50 UTC, w0rp wrote:
On Saturday, 11 April 2015 at 17:01:42 UTC, Dennis Ritchie
wrote:
Will the STL included in Phobos or is it impossible?
STL won't be included in Phobos, at least as far as I know, but
I believe it should be possible to interface to parts
On 04/12/2015 12:35 AM, weaselcat wrote:
> How does this differ from e.g, if the function was templated?
It doesn't, if you decide to analyze each imported function to perform
attribute inference, then that's just like treating all of them like
template instances.
This approach doesn't scale to bi
On Sunday, 12 April 2015 at 01:29:53 UTC, Idan Arye wrote:
On Saturday, 11 April 2015 at 22:29:58 UTC, w0rp wrote:
On Saturday, 11 April 2015 at 10:27:15 UTC, weaselcat wrote:
if you're using vim-dutyl you could just remap K to :DUjump
or one of the split variants.
(DUddoc also shows the docume
On Saturday, 11 April 2015 at 22:29:58 UTC, w0rp wrote:
On Saturday, 11 April 2015 at 10:27:15 UTC, weaselcat wrote:
if you're using vim-dutyl you could just remap K to :DUjump or
one of the split variants.
(DUddoc also shows the documentation of the symbol under your
cursor.)
I'll have to tr
On 04/05/2015 05:16 AM, Andrei Alexandrescu wrote:
> Right now the allocator design works well as a flexible malloc/free
> implementation, but has no support for tracing-based garbage collection.
>
> I am evaluating whether I should add tracing capabilities to
> std.allocator, or stop here. Tracin
On Saturday, 11 April 2015 at 10:24:53 UTC, Jakob Ovrum wrote:
I've done some preliminary work on a wiki page that attempts to
convince C++ programmers who are on the fence about D, who need
to know what D provides over C++11 and C++14.
http://wiki.dlang.org/Coming_From/C_Plus_Plus_WIP_article
On Thursday, 9 April 2015 at 14:03:33 UTC, Dicebot wrote:
On Thursday, 9 April 2015 at 04:30:18 UTC, Dicebot wrote:
On Wednesday, 1 April 2015 at 20:59:07 UTC, Dicebot wrote:
On Wednesday, 1 April 2015 at 20:40:02 UTC, Laeeth Isharc
wrote:
Experimenting on my oneplusone phone running arch
(gee
On Saturday, 11 April 2015 at 21:44:08 UTC, Iain Buclaw wrote:
No one announced (to me) it's existence. Thanks! I'll be sure
to check it out.
it also integrates DCD(combined with youcompleteme or similar
plugin gives intellisense-like completion,) and dscanner.
On Saturday, 11 April 2015 at 21:47:20 UTC, Martin Nowak wrote:
Option 1 isn't really viable because it turns into a whole
program
compilation model.
How does this differ from e.g, if the function was templated?
On Saturday, 11 April 2015 at 10:27:15 UTC, weaselcat wrote:
if you're using vim-dutyl you could just remap K to :DUjump or
one of the split variants.
(DUddoc also shows the documentation of the symbol under your
cursor.)
I'll have to try this myself. Vim has a feature for balloon
messages, s
Shouldn't the inference with analysis be possible when you have
the source available at least? You will still have to specify the
attributes in a .di file if you are statically or dynamically
linking to D libraries, but for source libraries or in parts of
your project, you should be able to per
Sorry to open yet another topic.
I'm repeatedly finding myself in situations where I write functions like
this.
private @property bool empty() const @safe pure nothrow @nogc
{
return impl is null || !impl.count;
}
This is obviously a joke, because the compiler very well knows
On 11 April 2015 at 12:27, weaselcat via Digitalmars-d
wrote:
> On Saturday, 11 April 2015 at 10:00:45 UTC, Iain Buclaw wrote:
>>
>> On 10 April 2015 at 21:19, Adam D. Ruppe via Digitalmars-d
>> wrote:
>>>
>>> On Friday, 10 April 2015 at 19:08:13 UTC, Paulo Pinto wrote:
- Move a me
On Saturday, 11 April 2015 at 09:28:46 UTC, Marc Schütz wrote:
It's not acceptable that it happens behind the user's back.
Costly operations must be explicit.
Nothing is costly here.
On Saturday, 11 April 2015 at 18:20:51 UTC, Marco Leise wrote:
Am Fri, 10 Apr 2015 14:04:39 +
schrieb "Ola Fosheim Grøstad"
:
On Friday, 10 April 2015 at 10:28:03 UTC, Walter Bright wrote:
> That's what ref counting is about.
That would require pervasive ref-counting.
You make is sound l
On 04/11/2015 01:03 PM, w0rp wrote:
> At the moment, auto-decoding isn't part of the language
That won't change anytime soon.
Am Fri, 10 Apr 2015 14:04:39 +
schrieb "Ola Fosheim Grøstad"
:
> On Friday, 10 April 2015 at 10:28:03 UTC, Walter Bright wrote:
> > That's what ref counting is about.
>
> That would require pervasive ref-counting.
You make is sound like there was an alternative to ref
counting for resources.
On Saturday, 11 April 2015 at 17:01:42 UTC, Dennis Ritchie wrote:
Will the STL included in Phobos or is it impossible?
STL won't be included in Phobos, at least as far as I know, but I
believe it should be possible to interface to parts of it with
extern(C++). To do it, you need to create nam
On Saturday, 11 April 2015 at 15:59:53 UTC, David Nadlinger wrote:
On Saturday, 11 April 2015 at 15:35:47 UTC, w0rp wrote:
[…] (Also LDC?) in druntime and flag all of the symbols like
this appropriately, so that creating executables with
gc-sections will Just Work in some cases without a linker
Will the STL included in Phobos or is it impossible?
On Saturday, 11 April 2015 at 15:35:47 UTC, w0rp wrote:
From what I just read, __attribute__((used)) in GCC should do
the job, and I think it should be usable from GDC with its
attribute pragmas.
I wouldn't mind having this functionality.
For a long time, I've wanted it in C in those cases w
On Saturday, 11 April 2015 at 10:24:53 UTC, Jakob Ovrum wrote:
http://wiki.dlang.org/Coming_From/C_Plus_Plus_WIP_article
*Un*signed integer overflow isn't undefined in C/C++ either.
— David
On 04/09/2015 01:10 AM, Walter Bright wrote:
> http://wiki.dlang.org/DIP77
It's a very interesting proposal to tackle this specific problem.
As with all the scope/lifetime related stuff, I find it extremely
difficult to anticipate all the needs and foresee how this will
integrate with the rest of
On Saturday, 11 April 2015 at 15:35:47 UTC, w0rp wrote:
[…] (Also LDC?) in druntime and flag all of the symbols like
this appropriately, so that creating executables with
gc-sections will Just Work in some cases without a linker
script?
LDC is shipping with --gc-sections enabled by default si
I've been looking into compiling smaller executables, and the
trick I learned from watching sessions from the last DConf is to
use the KEEP symbol in a linker script with something like
gc-sections. So at the compilation stage, symbols are put in
different sections, a linker script marks some s
On 12/04/2015 12:32 a.m., jkpl wrote:
On Saturday, 11 April 2015 at 09:11:35 UTC, Rikki Cattermole wrote:
On 11/04/2015 8:34 p.m., jkpl wrote:
On Saturday, 11 April 2015 at 07:28:50 UTC, Rikki Cattermole wrote:
On 11/04/2015 7:24 p.m., jkpl wrote:
On Saturday, 11 April 2015 at 05:45:10 UTC, R
On Saturday, 11 April 2015 at 11:33:51 UTC, Marc Schütz wrote:
On Saturday, 11 April 2015 at 09:41:07 UTC, Walter Bright wrote:
On 4/11/2015 2:28 AM, "Marc =?UTF-8?B?U2Now7x0eiI=?=
" wrote:
It's not acceptable that it happens behind the user's back.
Costly operations
must be explicit.
Don't
On Saturday, 11 April 2015 at 09:11:35 UTC, Rikki Cattermole
wrote:
On 11/04/2015 8:34 p.m., jkpl wrote:
On Saturday, 11 April 2015 at 07:28:50 UTC, Rikki Cattermole
wrote:
On 11/04/2015 7:24 p.m., jkpl wrote:
On Saturday, 11 April 2015 at 05:45:10 UTC, Rikki Cattermole
wrote:
On 11/04/2015 5
On Saturday, 11 April 2015 at 09:41:07 UTC, Walter Bright wrote:
On 4/11/2015 2:28 AM, "Marc =?UTF-8?B?U2Now7x0eiI=?=
" wrote:
It's not acceptable that it happens behind the user's back.
Costly operations
must be explicit.
Don't know of a better solution.
How about this?
http://wiki.dlang.
On Saturday, 11 April 2015 at 11:02:47 UTC, ponce wrote:
You should mention stack variables and members initialized by
default. This avoids many release-only bugs.
Also:
if (cond); // D won't allow that, but C++ will
statement();
Almost every C++ programmer encounter this in its c
On Saturday, 11 April 2015 at 10:24:53 UTC, Jakob Ovrum wrote:
I've done some preliminary work on a wiki page that attempts to
convince C++ programmers who are on the fence about D, who need
to know what D provides over C++11 and C++14.
http://wiki.dlang.org/Coming_From/C_Plus_Plus_WIP_article
You should mention stack variables and members initialized by
default. This avoids many release-only bugs.
Also:
if (cond); // D won't allow that, but C++ will
statement();
Almost every C++ programmer encounter this in its carreer.
On Friday, 10 April 2015 at 18:32:39 UTC, Andrei Alexandrescu
wrote:
On 4/10/15 10:28 AM, Steven Schveighoffer wrote:
On 4/10/15 11:57 AM, Andrei Alexandrescu wrote:
On 4/10/15 6:26 AM, Meta wrote:
On Friday, 10 April 2015 at 12:42:47 UTC, Steven
Schveighoffer wrote:
Plus, adding arr.empty int
On Saturday, 11 April 2015 at 10:14:00 UTC, w0rp wrote:
I think the one thing in the DIP I'm not sure of is the
definition of what is a reference counted object.
I believe it's still defined by DIP74?
http://wiki.dlang.org/DIP74
On Saturday, 11 April 2015 at 10:00:45 UTC, Iain Buclaw wrote:
On 10 April 2015 at 21:19, Adam D. Ruppe via Digitalmars-d
wrote:
On Friday, 10 April 2015 at 19:08:13 UTC, Paulo Pinto wrote:
- Move a method to another class located in another module,
while updating
all references to it, incl
I've done some preliminary work on a wiki page that attempts to
convince C++ programmers who are on the fence about D, who need
to know what D provides over C++11 and C++14.
http://wiki.dlang.org/Coming_From/C_Plus_Plus_WIP_article
I don't know if a Coming_From page is the right place for this
On Saturday, 11 April 2015 at 09:28:46 UTC, Marc Schütz wrote:
On Friday, 10 April 2015 at 23:12:55 UTC, deadalnix wrote:
On Friday, 10 April 2015 at 10:02:01 UTC, Martin Nowak wrote:
On Wednesday, 8 April 2015 at 23:11:08 UTC, Walter Bright
wrote:
http://wiki.dlang.org/DIP77
So someone pass
On 10 April 2015 at 21:19, Adam D. Ruppe via Digitalmars-d
wrote:
> On Friday, 10 April 2015 at 19:08:13 UTC, Paulo Pinto wrote:
>>
>> - Move a method to another class located in another module, while updating
>> all references to it, including module imports in the new file
>
>
> Cut the text out
On Saturday, 11 April 2015 at 08:35:18 UTC, Ola Fosheim Grøstad
wrote:
On Friday, 10 April 2015 at 15:44:32 UTC, Andrei Alexandrescu
wrote:
We hope to do better than Rust. -- Andrei
Hope does not cut it.
A design that breaks down even on a linked list (e.g. you have
to turn to ref-counted po
On 4/11/2015 2:28 AM, "Marc =?UTF-8?B?U2Now7x0eiI=?= " wrote:
It's not acceptable that it happens behind the user's back. Costly operations
must be explicit.
Don't know of a better solution.
On 4/11/2015 2:18 AM, "Marc =?UTF-8?B?U2Now7x0eiI=?= " wrote:
On Friday, 10 April 2015 at 21:26:14 UTC, Walter Bright wrote:
On 4/10/2015 11:28 AM, "Marc =?UTF-8?B?U2Now7x0eiI=?= " wrote:
Example:
void foo() @safe {
RCArray!int arr = [0,1,2];
{
int* p = &arr[0]; // legal under
On Friday, 10 April 2015 at 23:12:55 UTC, deadalnix wrote:
On Friday, 10 April 2015 at 10:02:01 UTC, Martin Nowak wrote:
On Wednesday, 8 April 2015 at 23:11:08 UTC, Walter Bright
wrote:
http://wiki.dlang.org/DIP77
So someone passes an RCO via ref to avoid the inc/dec, and
because that impose
On Saturday, 11 April 2015 at 09:15:19 UTC, Martin Nowak wrote:
On Friday, 10 April 2015 at 21:26:14 UTC, Walter Bright wrote:
This would be a bad design of an RCO. RCO's must be
constructed to not allow pointers to the payload other than by
ref.
And taking the address of that is already unsa
On Friday, 10 April 2015 at 21:26:14 UTC, Walter Bright wrote:
On 4/10/2015 11:28 AM, "Marc =?UTF-8?B?U2Now7x0eiI=?=
" wrote:
Example:
void foo() @safe {
RCArray!int arr = [0,1,2];
{
int* p = &arr[0]; // legal under new scope rules
This would be a bad design of an RCO. RCO's
I was thinking about this again, and how the first 'ref' would
create a copy in order to keep the object around. At first I
thought I didn't like that, but then I realised that it's
actually not far from what I wanted for taking r-values by
reference. I commonly write functions which take value
On Friday, 10 April 2015 at 21:26:14 UTC, Walter Bright wrote:
This would be a bad design of an RCO. RCO's must be constructed
to not allow pointers to the payload other than by ref.
And taking the address of that is already unsafe.
On 11/04/2015 8:34 p.m., jkpl wrote:
On Saturday, 11 April 2015 at 07:28:50 UTC, Rikki Cattermole wrote:
On 11/04/2015 7:24 p.m., jkpl wrote:
On Saturday, 11 April 2015 at 05:45:10 UTC, Rikki Cattermole wrote:
On 11/04/2015 5:43 p.m., Rashad Vinshy wrote:
CSGL:
I would like to announce the r
On 2015-04-10 21:02, Idan Arye wrote:
Many of these Vim users are not really Vim users - not in the sense that
Emacs users are Emacs users anyways. Sure, they use Vim - but only
because it's a default editor in Unix-like systems. If Windows Notepad
was the default text they wouldn't have install
On Friday, 10 April 2015 at 15:44:32 UTC, Andrei Alexandrescu
wrote:
We hope to do better than Rust. -- Andrei
Hope does not cut it.
A design that breaks down even on a linked list (e.g. you have to
turn to ref-counted pointers everywhere) and that makes
findByRef(container,node) break shoul
On Saturday, 11 April 2015 at 07:28:50 UTC, Rikki Cattermole
wrote:
On 11/04/2015 7:24 p.m., jkpl wrote:
On Saturday, 11 April 2015 at 05:45:10 UTC, Rikki Cattermole
wrote:
On 11/04/2015 5:43 p.m., Rashad Vinshy wrote:
CSGL:
I would like to announce the release of my beta library for
D!
Wh
On Saturday, 11 April 2015 at 05:43:14 UTC, Rashad Vinshy wrote:
CSGL:
I would like to announce the release of my beta library for D!
What is the best plan of action at this point to contribute it
to the D community? (the library still needs debugging and
optimization support, I've only teste
On Friday, 10 April 2015 at 23:04:44 UTC, Andrei Alexandrescu
wrote:
Martin Nowak added recently a nice feature to the Phobos
makefile: by specifying e.g.
make std/stdio.test
only the unittests for std/stdio.d would build and run. This
greatly improves development turnaround for Phobos.
FWI
On 11/04/2015 7:24 p.m., jkpl wrote:
On Saturday, 11 April 2015 at 05:45:10 UTC, Rikki Cattermole wrote:
On 11/04/2015 5:43 p.m., Rashad Vinshy wrote:
CSGL:
I would like to announce the release of my beta library for D!
What is the best plan of action at this point to contribute it to the D
c
On Saturday, 11 April 2015 at 05:45:10 UTC, Rikki Cattermole
wrote:
On 11/04/2015 5:43 p.m., Rashad Vinshy wrote:
CSGL:
I would like to announce the release of my beta library for D!
What is the best plan of action at this point to contribute it
to the D
community? (the library still needs de
62 matches
Mail list logo
