On 22 May 2018 at 22:06, VectorThis via Digitalmars-d
wrote:
> On Wednesday, 23 May 2018 at 04:38:48 UTC, Manu wrote:
>>
>>
>> Sure he does! It's a fair call.
>
>
> Hey, it could be worse, you could have wrote this below instead..
> (then imagine the chaos that would
Manu's rvalue DIP has gotten quite a bit of feedback already, but
I'll soon be prepping it for community review. If you'd like to
get some comments in before we get there, now's the time to do so.
https://github.com/dlang/DIPs/pull/111
Also, Walter has a draft DIP for adding a bottom type
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
I've often wondered if D has the right features to implement a
borrow-checker in the library. Something similar to this:
https://www.youtube.com/watch?v=Lj1GppqNr8c
On Wednesday, 23 May 2018 at 04:38:48 UTC, Manu wrote:
Sure he does! It's a fair call.
Hey, it could be worse, you could have wrote this below instead..
(then imagine the chaos that would unfold on the D forums)
extern(C++, SomethingHere)
{
void penetration();
void private();
}
On 23/05/2018 5:01 PM, Mike Franklin wrote:
On Wednesday, 23 May 2018 at 04:58:17 UTC, rikki cattermole wrote:
In essence a -betterC libc with wrapper functions for extern(D).
I'd prefer to not even need to link in libc. I mean rewrite memcpy,
memcmp, malloc, free, and realloc in D. Once
On Wednesday, 23 May 2018 at 04:58:17 UTC, rikki cattermole wrote:
In essence a -betterC libc with wrapper functions for extern(D).
I'd prefer to not even need to link in libc. I mean rewrite
memcpy, memcmp, malloc, free, and realloc in D. Once those
building blocks exist in D, everything
On Wednesday, 23 May 2018 at 04:17:19 UTC, Mike Franklin wrote:
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
Try to replace some of the basic software building blocks
(memcpy, memcmp, malloc, free, realloc) that are currently
leveraged from
On 23/05/2018 4:56 PM, Mike Franklin wrote:
On Wednesday, 23 May 2018 at 04:17:19 UTC, Mike Franklin wrote:
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
Try to replace some of the basic software building blocks (memcpy,
memcmp, malloc, free,
On Wednesday, 23 May 2018 at 01:18:43 UTC, Walter Bright wrote:
DigitalMars C/C++ Compiler (github.com)
56 points by tomcam 3 hours ago | unvote | flag | hide | 10
comments
Yay! Any thoughts about opening runtime library?
https://news.ycombinator.com/news
And it’s beyond 100+ now. Also
On 22 May 2018 at 21:31, rikki cattermole via Digitalmars-d
wrote:
> On 23/05/2018 4:29 PM, 12345swordy wrote:
>>
>> On Wednesday, 23 May 2018 at 03:44:36 UTC, Manu wrote:
>>>
>>>
>>> extern(C++, FuckOff)
>>> {
>>> void bah();
>>> void humbug();
>>> }
>>> alias
On Wednesday, 23 May 2018 at 03:45:39 UTC, Manu wrote:
... what?
Konw it off with the sex talk here.
On Wednesday, 23 May 2018 at 04:17:19 UTC, Mike Franklin wrote:
Try to replace some of the basic software building blocks
(memcpy, memcmp, malloc, free, realloc) that are currently
leveraged from the platform's C library with counterparts, and
provide a D API that uses `T[]` instead of void*
On 23/05/2018 4:29 PM, 12345swordy wrote:
On Wednesday, 23 May 2018 at 03:44:36 UTC, Manu wrote:
extern(C++, FuckOff)
{
void bah();
void humbug();
}
alias this FuckOff; // <-- symbols are now aliased where they should
have been all along
Knock it off with sex talk here.
This is Manu
On Wednesday, 23 May 2018 at 03:44:36 UTC, Manu wrote:
extern(C++, FuckOff)
{
void bah();
void humbug();
}
alias this FuckOff; // <-- symbols are now aliased where they
should
have been all along
Knock it off with sex talk here.
On 22 May 2018 at 20:53, Stefan Koch via Digitalmars-d
wrote:
> On Wednesday, 23 May 2018 at 03:44:36 UTC, Manu wrote:
>>
>> Okay, I'm still really angry about the stupid stupid decision to make C++
>> namespaces into scopes rather than just a detail used for
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
Try to replace some of the basic software building blocks
(memcpy, memcmp, malloc, free, realloc) that are currently
leveraged from the platform's C library with counterparts, and
provide a D API
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
Building and running the DMD test suite on vanilla Windows is a
pain. I never succeeded but it appears to require the user to
first set up a posix environment and then battle environment
On Wednesday, 23 May 2018 at 03:44:36 UTC, Manu wrote:
Okay, I'm still really angry about the stupid stupid decision
to make C++ namespaces into scopes rather than just a detail
used for mangling, with absolutely no consultation of the
community, in particular the target audience, who are
On 22 May 2018 at 19:39, 12345swordy via Digitalmars-d
wrote:
> On Wednesday, 23 May 2018 at 02:15:25 UTC, Manu wrote:
>>
>> It should recurse the ClassInfo calling the dtors there to perform a
>> full virtual destruction.
>
>
> Why? That seems restrictive as there is
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
An LDC or GDC cross-compiler generator for the Raspberry Pi.
There are already some instructions out there (e.g.
http://d-land.sepany.de/einstieg-in-die-raspberry-pi-entwicklung-mit-ldc.html), but
Okay, I'm still really angry about the stupid stupid decision to make
C++ namespaces into scopes rather than just a detail used for
mangling, with absolutely no consultation of the community, in
particular the target audience, who are unanimously annoyed as far as
I can tell...
I'm unsatisfied by
On Wednesday, 23 May 2018 at 03:19:15 UTC, VectorThis wrote:
so penetration is a bad word, cause 12345swordy says so?
"M15 had been penetrated by Russian intelligence"
oohh.. that's disgusting.
"they penetrated the enemy territory via a gap cut in the fence"
ohhh..that's even worse.
come
On Wednesday, 23 May 2018 at 03:11:15 UTC, 12345swordy wrote:
On Wednesday, 23 May 2018 at 02:56:33 UTC, VectorThis wrote:
All you want to do is attack this person, cause you don't
agree with the idea.
Strawman. I attack his usage of language, not the person.
so penetration is a bad word,
On Wednesday, 23 May 2018 at 02:56:33 UTC, VectorThis wrote:
All you want to do is attack this person, cause you don't agree
with the idea.
Strawman. I attack his usage of language, not the person.
On Wednesday, 23 May 2018 at 03:00:17 UTC, Nicholas Wilson wrote:
On Wednesday, 23 May 2018 at 02:24:08 UTC, IntegratedDimensions
wrote:
Many times in expensive loops one must make decisions.
Decisions must be determined and the determination costs.
for(int i = 0; i < N; i++)
{
On Wednesday, 23 May 2018 at 01:51:35 UTC, Mike Franklin wrote:
Make WebAssembly a thing in D.
Yes please!
I would love to help with WebAssembly in D but frankly it is a
little it overwhelming me and my lack of knowledge. If anyone
does take the bull by the horns, let me know if you need a
On Wednesday, 23 May 2018 at 02:24:08 UTC, IntegratedDimensions
wrote:
Many times in expensive loops one must make decisions.
Decisions must be determined and the determination costs.
for(int i = 0; i < N; i++)
{
if(decision(i)) A; else B;
}
the if statement costs N times the cycle
On Wednesday, 23 May 2018 at 02:49:51 UTC, 12345swordy wrote:
On Wednesday, 23 May 2018 at 02:34:35 UTC, Grady Booch wrote:
make unittests useful again, by not allowing them to
penetrate an objects private parts.
Knock it off with sex talk here.
really?
why don't you knock it off!!
All
On Wednesday, 23 May 2018 at 02:23:31 UTC, Bjarne Stroustrup
wrote:
This is NOT why I created C++ - just so you programmers could
violate an objects autonomy!
So why did you create C++?
On the serious side though, unencapsulated software is
inflexible, and as a result, not very robust.
On Wednesday, 23 May 2018 at 02:34:35 UTC, Grady Booch wrote:
make unittests useful again, by not allowing them to penetrate
an objects private parts.
Knock it off with sex talk here.
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
I haven't looked into this myself, but I vaguely remember an
ongoing problem with DMDs performance (especially memory usage)
gradually degrading with time. I think it would be a nice
exercise for
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
Fork newCTFE and bring it to completion:
https://dlang.org/blog/2017/04/10/the-new-ctfe-engine/
Mike
On Wednesday, 23 May 2018 at 02:15:25 UTC, Manu wrote:
It should recurse the ClassInfo calling the dtors there to
perform a
full virtual destruction.
Why? That seems restrictive as there is possibility that the
parent class have an empty destruction with no attributes which
your suggestion
On Wednesday, 23 May 2018 at 02:23:31 UTC, Bjarne Stroustrup
wrote:
This is NOT why I created C++
You are not Bjarne Stroustrup and you certainly did not created
C++.
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
Find a way to improve the performance of our CIs. See
https://forum.dlang.org/post/mailman.1018.1526887297.29801.digitalmar...@puremagic.com
The more time a PR is "green" the higher the
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Hello, everyone!
We, at UPB, have initiated D's participation to ROSEdu Summer
of Code, see http://soc.rosedu.org/2018/.
I will be mentoring a student over the summer and I was
wondering if you have
any suggestions for a
On Wednesday, 23 May 2018 at 02:23:31 UTC, Bjarne Stroustrup
wrote:
This is NOT why I created C++ - just so you programmers could
violate an objects autonomy!
No other type gets treated this way in D.
Good on you Bjarne. Someone has to stick up for the class.
We're with you Bjarne.
While
On Tuesday, 22 May 2018 at 13:33:12 UTC, 12345swordy wrote:
On Tuesday, 22 May 2018 at 03:10:39 UTC, Bjarne Stroustrup
wrote:
Any debate about restoring the rights and autonomy of the
class, should not be killed off.
Any programming language that discriminates against the class,
encourages
Many times in expensive loops one must make decisions. Decisions
must be determined and the determination costs.
for(int i = 0; i < N; i++)
{
if(decision(i)) A; else B;
}
the if statement costs N times the cycle cost.
In some cases the decision holds for continuous ranges. For some
0
On 22 May 2018 at 18:59, sarn via Digitalmars-d
wrote:
> (I'm referring to Scott's 2014 DConf talk:
> https://www.youtube.com/watch?v=KAWA1DuvCnQ)
>
> I was actually preparing a DIP about this when Manu posted to the forums
> about his own related problems with C++
On 23/05/2018 2:00 PM, Mike Franklin wrote:
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
An apprentice for Walter.
I think Walter needs an apprentice (or 10). Too much knowledge about
D's design decisions, present, and future are locked up
On 23/05/2018 1:59 PM, sarn wrote:
(I'm referring to Scott's 2014 DConf talk:
https://www.youtube.com/watch?v=KAWA1DuvCnQ)
I was actually preparing a DIP about this when Manu posted to the forums
about his own related problems with C++ interop.
I traced a bug in some of my D code to my own
On Tuesday, 22 May 2018 at 23:09:24 UTC, Sjoerd Nijboer wrote:
On Tuesday, 22 May 2018 at 22:17:05 UTC, IntegratedDimensions
wrote:
On Tuesday, 22 May 2018 at 22:10:52 UTC, Alex wrote:
On Tuesday, 22 May 2018 at 21:45:07 UTC, IntegratedDimensions
wrote:
an idea to lock data by removing the
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
Get some help allocated to GDC.
It seems progress on GDC has stalled for reasons I'm not quite
sure of. I'm trying to help, but it's becoming more apparent
that I'm not the right person for the
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
An apprentice for Walter.
I think Walter needs an apprentice (or 10). Too much knowledge
about D's design decisions, present, and future are locked up in
his mind. He needs to be disseminating
(I'm referring to Scott's 2014 DConf talk:
https://www.youtube.com/watch?v=KAWA1DuvCnQ)
I was actually preparing a DIP about this when Manu posted to the
forums about his own related problems with C++ interop.
I traced a bug in some of my D code to my own misunderstanding of
how D's
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
Make WebAssembly a thing in D.
See
https://forum.dlang.org/post/ejplfelcqsvjmdvxt...@forum.dlang.org
Currently C++ and Rust dominate that domain. D could kick some
web asm there too.
Mike
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
It might be useful for measuring D's progress if we had some kind
of stats about D updated on a daily basis.
This is the most useful page I know of at the moment:
On Tuesday, 22 May 2018 at 18:20:43 UTC, Robert M. Münch wrote:
I see that I'm writing
try {
... different code ...
} catch (myException e) {
... same handling code ...
}
over and over again.
Of course I can put the exception handling code into a function
to not duplicate it.
On 22 May 2018 at 06:44, Steven Schveighoffer via Digitalmars-d
wrote:
> On 5/22/18 1:01 AM, Manu wrote:
>>
>> On 21 May 2018 at 15:51, Steven Schveighoffer via Digitalmars-d
>> wrote:
>>>
>>> On 5/21/18 6:37 PM, Manu wrote:
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Let the brainstorming begin!
I would like to see a dependency-less Phobos-like library that
can be used by the DMD compiler, druntime, -betterC, and other
runtime-less/phobos-less use cases. It would have no
dependencies
https://issues.dlang.org/show_bug.cgi?id=18891
--- Comment #2 from Manu ---
This happens on my home PC and my work PC too. VS2015.
--
https://issues.dlang.org/show_bug.cgi?id=18642
--- Comment #6 from Manu ---
Emailed you the log (building DMD)
--
On 5/22/18 1:39 PM, jmh530 wrote:
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Hello, everyone!
We, at UPB, have initiated D's participation to ROSEdu Summer of Code,
see http://soc.rosedu.org/2018/.
I will be mentoring a student over the summer and I was wondering if
On Tuesday, 22 May 2018 at 22:17:05 UTC, IntegratedDimensions
wrote:
On Tuesday, 22 May 2018 at 22:10:52 UTC, Alex wrote:
On Tuesday, 22 May 2018 at 21:45:07 UTC, IntegratedDimensions
wrote:
an idea to lock data by removing the reference:
class A
{
Lockable!Data data;
}
The idea is that
On Tuesday, 22 May 2018 at 14:56:52 UTC, Ethan wrote:
Repeat ad infinitum for each slightly different configuration
you want. I always make the point of programmers being lazy by
definition, and not being able to do something as simple as
declare a type with a single statement is an clear
On Tuesday, 22 May 2018 at 22:10:52 UTC, Alex wrote:
On Tuesday, 22 May 2018 at 21:45:07 UTC, IntegratedDimensions
wrote:
an idea to lock data by removing the reference:
class A
{
Lockable!Data data;
}
The idea is that when the data is going to be used, the user
locks the data. The trick
On Tuesday, 22 May 2018 at 21:45:07 UTC, IntegratedDimensions
wrote:
an idea to lock data by removing the reference:
class A
{
Lockable!Data data;
}
The idea is that when the data is going to be used, the user
locks the data. The trick here is that data is a pointer to the
data and the
an idea to lock data by removing the reference:
class A
{
Lockable!Data data;
}
The idea is that when the data is going to be used, the user
locks the data. The trick here is that data is a pointer to the
data and the pointer is set to null when locked so no other data
can use it(they see
On Tuesday, 22 May 2018 at 20:34:34 UTC, Ethan wrote:
foreach( MemberName; __traits( allMembers, Parent ) )
{
if( MemberName == SymbolName )
{
mixin( "alias ThisSymbol = Alias!( " ~
fullyQualifiedName!Parent ~ "." ~ SymbolName ~ " );" );
This is another case of "Works for me!"
As a part of getting Binderoo working, I've long long long wanted
to automagically create typedefs from alias declarations. But
working out if something is an alias is difficult. For example:
struct SomeObject
{
int foo;
}
alias NotSomeObject =
On 5/22/18 3:58 PM, Dr.No wrote:
Does this cause infine loop?
https://github.com/schveiguy/jsoniopipe/blob/master/source/jsoniopipe/dom.d#L134
Possibly. Bug reports are welcome :) I think on this line, it will make
progress:
On Sunday, 17 December 2017 at 16:51:21 UTC, Steven Schveighoffer
wrote:
On 12/17/17 4:44 AM, Jonathan M Davis wrote:
[...]
There is an even more work-in-progress library built on that,
but it's not yet in dub (this was the library I wrote for my
dconf talk this year):
On Tuesday, 22 May 2018 at 13:33:12 UTC, 12345swordy wrote:
On Tuesday, 22 May 2018 at 03:10:39 UTC, Bjarne Stroustrup
wrote:
Any debate about restoring the rights and autonomy of the
class, should not be killed off.
Any programming language that discriminates against the class,
encourages
Hi!
Simple question to understand logic of quazi-multithreading:
Is Future.getResult blocks other tasks for end of "futured" task?
Or, another words, task.getResult causes task to ignore `yeilds`
inside of this task?
On Tuesday, 22 May 2018 at 00:30:22 UTC, SrMordred wrote:
We're working to get each talk into separate videos, but it
may take a while.
Thank you very much!
(for some odd reason the day 2 and 3 didn´t appear to me on
youtube when I searched)
The videos are marked "Unlisted" on Youtube. Can
On Tuesday, 22 May 2018 at 16:17:48 UTC, Russel Winder wrote:
Hi,
I have a shared object (of DInotify) compiled with ldc2.
I have a program (me-tv) which seems to work when compiled with
ldc2.
If I compile the program (me-tv) with dmd then it throws a
SIGSEGV seemingly
in
On 05/22/2018 11:20 AM, Robert M. Münch wrote:
I see that I'm writing
try {
... different code ...
} catch (myException e) {
... same handling code ...
}
over and over again.
Of course I can put the exception handling code into a function to not
duplicate it. However, I still need to
On 2018-05-22 20:20, Robert M. Münch wrote:
I see that I'm writing
try {
... different code ...
} catch (myException e) {
... same handling code ...
}
over and over again.
Of course I can put the exception handling code into a function to not
duplicate it. However, I still need to write
I see that I'm writing
try {
... different code ...
} catch (myException e) {
... same handling code ...
}
over and over again.
Of course I can put the exception handling code into a function to not
duplicate it. However, I still need to write this construct over and
over again. Is
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Hello, everyone!
We, at UPB, have initiated D's participation to ROSEdu Summer
Awsome! Come to Titu Maiorescu University too. Here, we love D,
some of us at least. :)
On Tuesday, 22 May 2018 at 16:27:05 UTC, Eduard Staniloiu wrote:
Hello, everyone!
We, at UPB, have initiated D's participation to ROSEdu Summer
of Code, see http://soc.rosedu.org/2018/.
I will be mentoring a student over the summer and I was
wondering if you have
any suggestions for a
https://issues.dlang.org/show_bug.cgi?id=18864
--- Comment #3 from Atila Neves ---
Using digger to build dmd 2.080.0 works and produces a 64-bit binary. Given
that digger uses a relatively old dmd to do so, it would seem the issue arises
when using 2.080.0 to build itself.
On Tuesday, 22 May 2018 at 16:17:48 UTC, Russel Winder wrote:
Hi,
I have a shared object (of DInotify) compiled with ldc2.
I have a program (me-tv) which seems to work when compiled with
ldc2.
If I compile the program (me-tv) with dmd then it throws a
SIGSEGV seemingly
in
On Monday, 21 May 2018 at 22:09:08 UTC, SrMordred wrote:
There is some place where I can find this year conference
videos with or without slides?
Thanks!
They're starting to be posted:
https://www.youtube.com/user/hlmceventsgmbh
Hello, everyone!
We, at UPB, have initiated D's participation to ROSEdu Summer of
Code, see http://soc.rosedu.org/2018/.
I will be mentoring a student over the summer and I was wondering
if you have
any suggestions for a project. If there is a library or feature
that you would like
just
Hi,
I have a shared object (of DInotify) compiled with ldc2.
I have a program (me-tv) which seems to work when compiled with ldc2.
If I compile the program (me-tv) with dmd then it throws a SIGSEGV seemingly
in
_D3std4file15DirIteratorImpl5frontMFNdNfZSQBoQBn8DirEntry
in DInotify. Is this
On Tuesday, 22 May 2018 at 15:25:47 UTC, Jonathan M Davis wrote:
Honestly, I hate named argumts in general. This situation is
one of the few places I've ever run into where I thought that
they made any sense. [snip]
It's quite literally the only reason I ever want named arguments.
On Monday, 21 May 2018 at 22:21:34 UTC, Manu wrote:
On 21 May 2018 at 09:22, Jonathan Marler via Digitalmars-d
wrote:
On Monday, 21 May 2018 at 04:46:15 UTC, Manu wrote:
This CI situation with the DMD/druntime repos is not okay.
It takes ages... **hours**
https://issues.dlang.org/show_bug.cgi?id=6005
Dmitry Olshansky changed:
What|Removed |Added
CC|
https://issues.dlang.org/show_bug.cgi?id=5788
Dmitry Olshansky changed:
What|Removed |Added
Keywords||bootcamp,
https://issues.dlang.org/show_bug.cgi?id=5714
Dmitry Olshansky changed:
What|Removed |Added
Keywords||bootcamp
On Tuesday, May 22, 2018 14:53:50 Jacob Carlborg via Digitalmars-d wrote:
> On Tuesday, 22 May 2018 at 11:08:13 UTC, Jonathan M Davis wrote:
> > That's basically what dxml does except that it takes advantage
> > of the fact that each member is a different type (because each
> > is a differnt
On Tuesday, 22 May 2018 at 13:30:02 UTC, Vladimir Panteleev wrote:
On Tuesday, 22 May 2018 at 13:11:00 UTC, Atila Neves wrote:
On Thursday, 17 May 2018 at 03:28:33 UTC, Vladimir Panteleev
wrote:
digger build --model=64
If you don't have Digger yet, you can run it straight from
Dub:
dub
https://issues.dlang.org/show_bug.cgi?id=5688
Dmitry Olshansky changed:
What|Removed |Added
Status|NEW |RESOLVED
On Monday, 21 May 2018 at 14:36:32 UTC, Jacob Carlborg wrote:
enum Options options = { foo: true, bar: false, a: 42, b:
"guess what this does" };
SomeObject!options o;
Yeah, so this is one reason why I went the parsing way.
enum Options Options1 = { foo: false, a: 5 };
SomeObject!Options1
https://issues.dlang.org/show_bug.cgi?id=5669
Dmitry Olshansky changed:
What|Removed |Added
CC|
On Tuesday, 22 May 2018 at 11:08:13 UTC, Jonathan M Davis wrote:
That's basically what dxml does except that it takes advantage
of the fact that each member is a different type (because each
is a differnt instance of std.typecons.Flag) so that it can
have a variadic function which takes any
On Tuesday, May 22, 2018 13:48:16 aliak via Digitalmars-d-learn wrote:
> On Monday, 21 May 2018 at 18:53:19 UTC, Jonathan M Davis wrote:
> > writeln = "foo";
> >
> > is legal, and it's dumb, but it hasn't mattered much in
> > practice. So, causing a bunch of code breakage in order to
> > disallow
https://issues.dlang.org/show_bug.cgi?id=18895
Issue ID: 18895
Summary: VisualD is unable to build dxml project
Product: D
Version: D2
Hardware: x86
OS: Windows
Status: NEW
Severity: enhancement
On 5/22/18 9:48 AM, aliak wrote:
On Monday, 21 May 2018 at 18:53:19 UTC, Jonathan M Davis wrote:
writeln = "foo";
is legal, and it's dumb, but it hasn't mattered much in practice. So,
causing a bunch of code breakage in order to disallow it is unlikely
to go over well. It would also then
On 5/22/18 4:40 AM, Robert M. Münch wrote:
On 2018-05-21 18:55:36 +, Steven Schveighoffer said:
When you use the alias, both are using the same exact lambda.
Ok. I didn't expect that the name is relevant in this case, instead
assumed that only the types need to match.
The type is the
On Monday, 21 May 2018 at 18:53:19 UTC, Jonathan M Davis wrote:
writeln = "foo";
is legal, and it's dumb, but it hasn't mattered much in
practice. So, causing a bunch of code breakage in order to
disallow it is unlikely to go over well. It would also then
make getters and setters
On 5/22/18 1:01 AM, Manu wrote:
On 21 May 2018 at 15:51, Steven Schveighoffer via Digitalmars-d
wrote:
On 5/21/18 6:37 PM, Manu wrote:
On 21 May 2018 at 15:29, Steven Schveighoffer via Digitalmars-d
wrote:
Uninitialized, but
On 5/22/18 12:57 AM, Manu wrote:
On 21 May 2018 at 15:39, Steven Schveighoffer via Digitalmars-d
wrote:
On 5/21/18 6:26 PM, Manu wrote:
On 21 May 2018 at 14:53, Jonathan M Davis via Digitalmars-d
wrote:
On Monday, May 21, 2018
On Tuesday, 22 May 2018 at 03:10:39 UTC, Bjarne Stroustrup wrote:
Any debate about restoring the rights and autonomy of the
class, should not be killed off.
Any programming language that discriminates against the class,
encourages class warfare, does not deserve to be called a
programming
On Tuesday, 22 May 2018 at 13:11:00 UTC, Atila Neves wrote:
On Thursday, 17 May 2018 at 03:28:33 UTC, Vladimir Panteleev
wrote:
digger build --model=64
If you don't have Digger yet, you can run it straight from Dub:
dub fetch digger
dub run digger -- build --model=64
I keep forgetting about
On 5/21/18 11:44 PM, Walter Bright wrote:
On 5/21/2018 2:41 PM, Steven Schveighoffer wrote:
Will this really work?
I mean, if the compiler can see the implementation of S, even though
it's private, can't it inline things and screw with the binary
compatibility?
That's right. To avoid
On Thursday, 17 May 2018 at 03:28:33 UTC, Vladimir Panteleev
wrote:
On Tuesday, 15 May 2018 at 16:01:28 UTC, Atila Neves wrote:
I just spent 45min trying to build 64-bit dmd on Windows. It
wasn't fun. "Isn't it just make -f win64.mak?", I hear you
ask. Yes. If you want a version with debug
https://issues.dlang.org/show_bug.cgi?id=5283
--- Comment #2 from Jonathan M Davis ---
(In reply to Dmitry Olshansky from comment #1)
> Jonathan, do you customizable test runner that D currently has still not
> addresses this? Including ready-made cutomizations such
1 - 100 of 133 matches
Mail list logo