On Tuesday, 16 February 2016 at 11:08:28 UTC, Timon Gehr wrote:
On 16.02.2016 11:21, krzaq wrote:
By the way, your example in C++ would be even worse:
auto sum_of_filtered = x
.map([&](auto&& val){ foo(val); })
.filter([](auto&& val){ return is_bar(val); })
https://issues.dlang.org/show_bug.cgi?id=15693
Jacob Carlborg changed:
What|Removed |Added
CC||d...@me.com
--- Comment #3
On Wednesday, 17 February 2016 at 02:44:04 UTC, Matt Elkins wrote:
On Wednesday, 17 February 2016 at 02:23:52 UTC, Ali Çehreli
wrote:
[...]
Oof. This strikes me as a "gotcha", that this happens even with
@disable this() as opposed to a compiler error. Is this only
for static arrays, or are
On 2/17/16 1:58 AM, Rikki Cattermole wrote:
A few things:
https://github.com/schveiguy/iopipe/blob/master/source/iopipe/traits.d#L126
why isn't that used more especially with e.g. window?
After all, window seems like a very well used word...
Not sure what you mean.
I don't like that a
On 17/02/16 7:45 PM, Steven Schveighoffer wrote:
It's no secret that I've been looking to create an updated io library
for phobos. In fact, I've been working on one on and off since 2011 (ouch).
After about 5 iterations of API and design, and testing out ideas, I
think I have come up with
On Tuesday, 16 February 2016 at 17:15:17 UTC, Jardík wrote:
But if I couldn't use GC and do all allocations and
deallocations manually, I wouldn't even be able to use
exceptions and there would also no longer be much reason to
write it in D.
I'd say if you're going to grow GC heap so big it
It's no secret that I've been looking to create an updated io library
for phobos. In fact, I've been working on one on and off since 2011 (ouch).
After about 5 iterations of API and design, and testing out ideas, I
think I have come up with something pretty interesting. It started out
as a
On 2/16/2016 9:56 PM, Ola Fosheim Grøstad wrote:
1. The compiler has access to all reachable types.
Nope. Opaque types are supported.
On Wednesday, 17 February 2016 at 02:51:06 UTC, Walter Bright
wrote:
The trouble with that is you're relying on the programmer to
ensure correctness. It'll revert D to C++ "trust the
programmer" semantics.
You might end up in a worse position than C++, as people will
cast away constness /
On Wednesday, 17 February 2016 at 03:40:38 UTC, maxinechar wrote:
The manga about kantai collection is so popular, now I can play
the game based on this comic. But it is my first time played
this game, can you help me with this game?
No.
On Wednesday, 17 February 2016 at 02:32:01 UTC, bachmeier wrote:
You can discuss here, but there is also a gitter room
https://gitter.im/DlangScience/public
Also, I've got a project that embeds R inside D
http://lancebachmeier.com/rdlang/
It's not quite as good a user experience as others
https://issues.dlang.org/show_bug.cgi?id=15693
--- Comment #2 from Walter Bright ---
At the very least, the dmd.2.070.tar.tar file is corrupted.
--
https://issues.dlang.org/show_bug.cgi?id=15693
--- Comment #1 from Walter Bright ---
Apparently the command switch to use is -zxvf, but that produces the same error
message.
--
The manga about kantai collection is so popular, now I can play
the game based on this comic. But it is my first time played this
game, can you help me with this game?
https://issues.dlang.org/show_bug.cgi?id=15693
Issue ID: 15693
Summary: Peculiar problems with OSX archive
Product: D
Version: D2
Hardware: All
OS: Mac OS X
Status: NEW
Severity: blocker
Priority:
On 02/17/2016 04:44 AM, Walter Bright wrote:
> Note that head const does not introduce any watering down nor
> destruction of the const/immutable/sharing type system. The main
> downside of head const would be language complexity.
Yes, I agree - it isn't like head const is bad on its own, it
On 2/16/2016 6:20 PM, Dicebot wrote:
The problem with this DIP is that it speaks about type system semantics
and what matters first is memory model (which is currently very
under-defined as soon as you step from a "the GC" world).
Physical immutability is demanding but it also has great value
On 2/16/2016 11:29 AM, Marc Schütz wrote:
For example, it's always possible to use a global mutable associative array to
store additional data connected with an immutable or const object (ignoring
purity issues for the moment). That's safe because from the outside, there's no
observable change
On 2/16/2016 5:35 AM, Dicebot wrote:
In my opinion @mutable would be a disaster of much higher destructive
impact than head const. I am very opposed to it no matter how it is
designed. Once you start considering it, you are better at simply
throwing away existing const system and starting it all
On Wednesday, 17 February 2016 at 02:23:52 UTC, Ali Çehreli wrote:
Since a static array must consist of .init values to begin
with, every move into its members must also trigger its
destructor if the type has elaborate destructor.
Oof. This strikes me as a "gotcha", that this happens even
On Wednesday, 17 February 2016 at 02:03:40 UTC, Jon D wrote:
On Tuesday, 16 February 2016 at 16:27:27 UTC, bachmeier wrote:
On Monday, 15 February 2016 at 11:09:10 UTC, data pulverizer
wrote:
As an alternative are there plans for parallel/cluster
computing frameworks for D?
You can use
On 02/16/2016 05:50 PM, Matt Elkins wrote:
On Tuesday, 16 February 2016 at 08:18:51 UTC, Ali Çehreli wrote:
When a temporary Foo object is moved into the array, the temporary
object is set to Foo.init. This temporary object lives on the stack.
In fact, all temporary Foo objects of Foo.this(int)
On Wednesday, 17 February 2016 at 02:23:34 UTC, cym13 wrote:
Such errors are static errors, they aren't allocated on the
stack, a 128 bytes buffer is shared accross threads to keep
them.
Sorry, of course I meant they *are* allocated on the stack.
On Tuesday, 16 February 2016 at 17:15:17 UTC, Jardík wrote:
But if I couldn't use GC and do all allocations and
deallocations manually, I wouldn't even be able to use
exceptions and there would also no longer be much reason to
write it in D. I did some searching and came into discussion
and
On 02/16/2016 09:29 PM, Marc Schütz wrote:
> The last sentence in my post is crucial: "keep most of the existing
> guarantees". If we can ensure that access to @mutable data is strongly
> restricted and properly encapsulated, we don't lose anything. The type
> system would stay as it is, there
After some more time spent on (the non-reduced version of) this,
I think there is a decent chance I am really just experiencing
another manifestation of a bug I reported a little bit ago:
https://issues.dlang.org/show_bug.cgi?id=15661
The good news is that this is now marked as resolved, so
On Tuesday, 16 February 2016 at 16:27:27 UTC, bachmeier wrote:
On Monday, 15 February 2016 at 11:09:10 UTC, data pulverizer
wrote:
As an alternative are there plans for parallel/cluster
computing frameworks for D?
You can use MPI:
https://github.com/DlangScience/OpenMPI
FWIW, I'm
On Tuesday, 16 February 2016 at 10:45:09 UTC, Marc Schütz wrote:
On Tuesday, 16 February 2016 at 04:00:27 UTC, Mike Parker wrote:
On Tuesday, 16 February 2016 at 03:39:00 UTC, Matt Elkins
wrote:
On Tuesday, 16 February 2016 at 03:31:51 UTC, maik klein
wrote:
In D you can always call Foo.init
On Tuesday, 16 February 2016 at 08:18:51 UTC, Ali Çehreli wrote:
When a temporary Foo object is moved into the array, the
temporary object is set to Foo.init. This temporary object
lives on the stack. In fact, all temporary Foo objects of
Foo.this(int) live at the same location.
After Foo(8)
On 17/02/16 1:19 PM, Seb wrote:
I am still in the process of learning D - it's a fantastic language.
Thanks so much!
However there is one thing that I came by which I think is a bit
annoying and could be easily solved - there seems to be no way to
combine `front` and `popFront` in one call even
Hello, I have a problem with using std.range.choose():
When using std.range.choose() on a range R, for which
hasElaborateCopyConstructor!R is true, then a postblit for the
result of std.range.choose() is created, which includes a call to
R.__postblit(). However, hasElaborateCopyConstructor!R
Sorry, this is the rest of the program: :)
struct S {
int i;
static size_t copyCount;
this(this) {
++copyCount;
if (!(copyCount % 2)) {
throw new Exception("Failed to copy S");
}
}
}
auto next(Range)(ref Range a){
auto b = a.front;
On Wednesday, 17 February 2016 at 00:45:35 UTC, Chris Wright
wrote:
http://dpldocs.info/search/search?searchTerm=emplace to create
an exception object in manually allocated memory.
Aye, this overload:
http://dpldocs.info/experimental-docs/std.conv.emplace.3.html
though the example there is
On 02/16/2016 04:19 PM, Seb wrote:
> However there is one thing that I came by which I think is a bit
> annoying and could be easily solved - there seems to be no way to
> combine `front` and `popFront` in one call even tough this use case
> seems quite frequently to me.
Although it seems
Can confirm -- in the hello world windows form application,
calling Runtime.initialize(); causes an access violation.
On Tue, 16 Feb 2016 10:35:38 -0200, Leandro Motta Barros via
Digitalmars-d-learn wrote:
> You probably already though of it, but: can't you create a unittest that
> calls your code as many times as desired, passing different input each
> time?
dmd -cov doesn't look specifically at unittests, so
On Tue, 16 Feb 2016 17:35:02 +, Adam D. Ruppe wrote:
> On Tuesday, 16 February 2016 at 17:15:17 UTC, Jardík wrote:
>> But if I couldn't use GC and do all allocations and deallocations
>> manually, I wouldn't even be able to use exceptions and there would
>> also no longer be much reason to
https://issues.dlang.org/show_bug.cgi?id=15686
--- Comment #2 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/D-Programming-Language/phobos
https://github.com/D-Programming-Language/phobos/commit/73bd032bbd7ae79b44b5328e64b868899aeb1377
fix issue 15686 -
On Tuesday, 16 February 2016 at 15:39:15 UTC, Adam D. Ruppe wrote:
On Tuesday, 16 February 2016 at 13:46:16 UTC, Craig Dillabaugh
wrote:
And as backup mentors
Adam D. Ruppe
My time has been extremely limited lately... if it is anything
more than answering some quick emails/irc chats every
I am still in the process of learning D - it's a fantastic
language. Thanks so much!
However there is one thing that I came by which I think is a bit
annoying and could be easily solved - there seems to be no way to
combine `front` and `popFront` in one call even tough this use
case seems
speaking as a lay user - if this is going to be done maybe it should
something like
__gconst?
similiar to __gshared which is ugly enough to make you concider not
using it, but it's there if you really need it.
On Wed, Feb 17, 2016 at 5:29 AM, Marc Schütz via Digitalmars-d
https://issues.dlang.org/show_bug.cgi?id=10378
--- Comment #24 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/D-Programming-Language/dmd
https://github.com/D-Programming-Language/dmd/commit/e5be0735919ce89dca7488e72229823d4a221773
fix Issue 10378 - Local
On Tuesday, 16 February 2016 at 18:30:43 UTC, Nick wrote:
Hey folks
I'm making a vibe.d application. Once a day it needs to
download some data. How do i get the program to perform this
task once a day?
Regards, Nick
You can use `Timer`. See `setTimer`/`createTimer` in
https://issues.dlang.org/show_bug.cgi?id=15686
ag0ae...@gmail.com changed:
What|Removed |Added
Keywords||pull
CC|
Oh, kuddos for the nice library.
On Monday, 8 February 2016 at 13:23:40 UTC, Atila Neves wrote:
What's new:
[...]
Enjoy!
Atila
I just started using unit-threaded and I like it so far,
specially the parallel runner. Just had some speed-bumps that
might be worth noting.
Before going into details I want to mention that I
On Tue, 16 Feb 2016 18:30:43 +, Nick wrote:
> Hey folks
>
> I'm making a vibe.d application. Once a day it needs to download some
> data. How do i get the program to perform this task once a day?
>
> Regards, Nick
http://vibed.org/api/vibe.core.core/runTask
On Tuesday, 16 February 2016 at 19:49:55 UTC, H. S. Teoh wrote:
On Tue, Feb 16, 2016 at 07:34:07PM +, Jon D via
Digitalmars-d-learn wrote:
On Tuesday, 16 February 2016 at 16:37:07 UTC, Steven
Schveighoffer wrote:
>On 2/14/16 10:22 PM, Jon D wrote:
>>Is there a way to reserve capacity in
On Tuesday, 16 February 2016 at 19:03:13 UTC, Zoadian wrote:
I'll write derelict bindings.
600 lines of code to display a triangle...
This is crying for toolkits. I guess they will emerge on github
soon.
https://issues.dlang.org/show_bug.cgi?id=15687
Jonathan M Davis changed:
What|Removed |Added
CC|
https://issues.dlang.org/show_bug.cgi?id=15675
Martin Krejcirik changed:
What|Removed |Added
Summary|BinaryHeap!(Array!T) is |[REG2.069]
On Tue, Feb 16, 2016 at 07:34:07PM +, Jon D via Digitalmars-d-learn wrote:
> On Tuesday, 16 February 2016 at 16:37:07 UTC, Steven Schveighoffer wrote:
> >On 2/14/16 10:22 PM, Jon D wrote:
> >>Is there a way to reserve capacity in associative arrays?
> >>[snip]
> >>The underlying implementation
On Tuesday, 16 February 2016 at 16:37:07 UTC, Steven
Schveighoffer wrote:
On 2/14/16 10:22 PM, Jon D wrote:
Is there a way to reserve capacity in associative arrays?
[snip]
The underlying implementation of associative arrays
appears to take an initial number of buckets, and there's
a private
I had one case these days in which I also had a lot of data to use in the
test. I was able to put the data as very large regular D arrays, but this
increased my compilation times a lot (not to mention the time to run the
unit tests).
I decided to enclose this specific unit test (including the
On Tuesday, 16 February 2016 at 13:35:56 UTC, Dicebot wrote:
On 02/16/2016 02:49 PM, Marc Schütz wrote:
`@mutable` OTOH would be a useful for both C++, reference
counting, caching, lazy initialization... But we need to find
a way to keep most of the existing guarantees, especially
concerning
On Tuesday, 16 February 2016 at 19:00:19 UTC, Ali Çehreli wrote:
std.traits.TemplateArgsOf:
http://dlang.org/phobos/std_traits.html#TemplateArgsOf
import std.traits;
class Foo(type1,type2)
{}
class Bar(FooType)
{
// pragma(msg, TemplateArgsOf!FooType);
alias ReturnType =
On Tuesday, 16 February 2016 at 18:28:19 UTC, Laeeth Isharc wrote:
I guess I feel that I could say that if it isn't solving a
significant real problem in the real world it isn't really
Forth.
Completely wrong, it was called Postscript, ran on laser printers
and solved a significant real
On 02/16/2016 10:34 AM, Gavin Maye wrote:
Say you have
class Foo(type1,type2)
{
}
And a concrete Foo is passed as a parameter to another template, is
there a way to get type1 and type2 from Foo so you can use them in the
new template... For example..
class Bar(FooType)
{
On 17/02/16 8:03 AM, Zoadian wrote:
On Tuesday, 16 February 2016 at 14:20:51 UTC, Ola Fosheim Grøstad wrote:
https://www.khronos.org/vulkan/
OS-X Metal is kinda like a C++ derivative => GPU compilation.
With Vulkan/SPIR other languages should be able to come up with
something similar for
On Tuesday, 16 February 2016 at 14:20:51 UTC, Ola Fosheim Grøstad
wrote:
https://www.khronos.org/vulkan/
OS-X Metal is kinda like a C++ derivative => GPU compilation.
With Vulkan/SPIR other languages should be able to come up with
something similar for other platforms.
finally.
I'll write
Hello Vulkan API 1.0 is here and I just wrapped it into D.
https://github.com/Rikarin/VulkanizeD
Have fun!
On Tuesday, 16 February 2016 at 12:35:38 UTC, Leandro Motta
Barros wrote:
You probably already though of it, but: can't you create a
unittest that calls your code as many times as desired, passing
different input each time?
That is a viable option yes. I will probably end up doing it like
On Saturday, 6 February 2016 at 06:29:56 UTC, cy wrote:
I don't see anything analagous to what std.stream does in
phobos... has it just not been made public yet?
This was actually something that kind of killed my vibe when I
was working on a project recently. I wanted to use some interface
Say you have
class Foo(type1,type2)
{
}
And a concrete Foo is passed as a parameter to another template,
is there a way to get type1 and type2 from Foo so you can use
them in the new template... For example..
class Bar(FooType)
{
FooType.type1 DoSomething() { ... }
}
or Even
On Tuesday, 16 February 2016 at 17:05:11 UTC, Basile B. wrote:
On Tuesday, 16 February 2016 at 16:37:07 UTC, Steven
Schveighoffer wrote:
There is not a public way to access these methods
unfortunately.
It would be a good addition to druntime I believe.
-Steve
After reading the topic i've
Hey folks
I'm making a vibe.d application. Once a day it needs to download
some data. How do i get the program to perform this task once a
day?
Regards, Nick
On Tuesday, 16 February 2016 at 18:06:05 UTC, karabuta wrote:
Hahaha. Well, I think it is already happening. Like the
reincarnation of C to C++ story.
The focus on interfacing D with C++ lately has been very
disconcerting, especially considering features from TDPL are
still unfinished
On Tuesday, 16 February 2016 at 11:43:05 UTC, Joakim wrote:
On Tuesday, 16 February 2016 at 10:20:57 UTC, Laeeth Isharc
wrote:
http://www.nature.com/news/the-chips-are-down-for-moore-s-law-1.19338
Good news for D and other AoT-compiled languages, as software
will have to take up the slack.
On Tuesday, 16 February 2016 at 06:04:42 UTC, Jonathan M Davis
wrote:
On Monday, 15 February 2016 at 22:48:16 UTC, Walter Bright
wrote:
rears its head again :-)
Head Const is what C++ has for const, i.e. it is not
transitive, applies to one level only. D has transitive const.
What head
Thanks for the info.
On Sunday, 14 February 2016 at 22:07:27 UTC, Tanel Tagaväli wrote:
+ Use SDL2 wrappings in GFM as a base
On second thought, abstracting platform-specific APIs seems a
better idea.
Would allow for more control, require less dependencies and I'm
sure there are other good reasons.
On Tuesday, 16 February 2016 at 17:15:17 UTC, Jardík wrote:
But if I couldn't use GC and do all allocations and
deallocations manually, I wouldn't even be able to use
exceptions and there would also no longer be much reason to
write it in D.
You can use exceptions without the GC and D offers
But if I couldn't use GC and do all allocations and deallocations
manually, I wouldn't even be able to use exceptions and there
would also no longer be much reason to write it in D. I did some
searching and came into discussion and there found out that in
case of an error thrown, D just
https://issues.dlang.org/show_bug.cgi?id=15675
Dragos Carp changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
On Tuesday, 16 February 2016 at 16:37:07 UTC, Steven
Schveighoffer wrote:
There is not a public way to access these methods unfortunately.
It would be a good addition to druntime I believe.
Recently, I added a clear method to the AA, which does not
reduce capacity. So if you frequently build
On Tuesday, 16 February 2016 at 16:27:54 UTC, Jonathan M Davis
wrote:
considerably. Andrei recently posted about possibly having a
reference count be in the memory next to an immutable object
but not having it in the object itself, and that might work:
I don't think I understand the semantic
https://issues.dlang.org/show_bug.cgi?id=15675
--- Comment #2 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/D-Programming-Language/phobos
https://github.com/D-Programming-Language/phobos/commit/b1537b3cb04d7714a8188e37e9a67191d21f26d9
Issue 15675 -
On 2/14/16 10:22 PM, Jon D wrote:
Is there a way to reserve capacity in associative arrays? In some
programs I've been writing I've been getting reasonable performance up
to about 10 million entries, but beyond that performance is impacted
considerably (say, 30 million or 50 million entries). GC
On Monday, 15 February 2016 at 11:09:10 UTC, data pulverizer
wrote:
As an alternative are there plans for parallel/cluster
computing frameworks for D?
You can use MPI:
https://github.com/DlangScience/OpenMPI
On Tuesday, 16 February 2016 at 16:01:26 UTC, Ola Fosheim Grøstad
wrote:
On Tuesday, 16 February 2016 at 15:33:03 UTC, Jonathan M Davis
wrote:
So, having @mutable would be far better than having it be
defined behavior to cast away const and mutate (assuming that
the underlying data is mutable
On Monday, 15 February 2016 at 22:48:16 UTC, Walter Bright wrote:
rears its head again :-)
Head Const is what C++ has for const, i.e. it is not
transitive, applies to one level only. D has transitive const.
What head const will do for us:
1. make it easy to interface to C++ code that uses
On Tuesday, 16 February 2016 at 15:33:03 UTC, Jonathan M Davis
wrote:
const guarantees that the data will not be mutated via that
reference to the data. It guarantees nothing about other
references to that data. For that, you need immutable.
Yes, it's as weak as C++ const in most cases from
On Tuesday, 16 February 2016 at 15:26:11 UTC, Andrei Alexandrescu
wrote:
On 2/16/16 8:46 AM, Craig Dillabaugh wrote:
[...]
You may want to scrape the email addresses of these folks and
send them email directly. -- Andrei
Good idea, I will try and hunt some of them down.
On Tuesday, 16 February 2016 at 15:03:36 UTC, Jakob Jenkov wrote:
I cannot speak on behalf of the D community. In my opinion I
don't think that it is D that needs a big data strategy. It is
the users of D that need that strategy.
I am originally a Java developer. Java devs. create all kinds
On Tuesday, 16 February 2016 at 06:04:42 UTC, Jonathan M Davis
wrote:
On Monday, 15 February 2016 at 22:48:16 UTC, Walter Bright
wrote:
rears its head again :-)
Head Const is what C++ has for const, i.e. it is not
transitive, applies to one level only. D has transitive const.
In this
On Tuesday, 16 February 2016 at 15:12:00 UTC, Ola Fosheim Grøstad
wrote:
On Tuesday, 16 February 2016 at 15:10:40 UTC, Timon Gehr wrote:
Legal.
Ouch... :-/
const guarantees that the data will not be mutated via that
reference to the data. It guarantees nothing about other
references to
On Thursday, 11 February 2016 at 19:36:09 UTC, default0 wrote:
On Thursday, 11 February 2016 at 17:09:40 UTC, Ben Palmer wrote:
Hi All,
The February Berlin D Meetup will be happening at 19:30 on
Friday the 19th at Berlin Co-Op (http://co-up.de/) on the
fifth floor.
This time Stefan Brus
On 2/16/16 8:46 AM, Craig Dillabaugh wrote:
The Google Summer of Code deadline is this Friday.
I would like confirmation from the following individuals if they can
mentor GSOC this summer.
Iain Buclaw
Bruno Medeiros
Martin Nowak (and as backup Admin)
Jacob Ovrum
And as backup mentors
Adam
On Tuesday, 16 February 2016 at 15:10:40 UTC, Timon Gehr wrote:
Legal.
Ouch... :-/
On 16.02.2016 14:41, Ola Fosheim Grøstad wrote:
On Tuesday, 16 February 2016 at 13:35:56 UTC, Dicebot wrote:
matter how it is designed. Once you start considering it, you are
better at simply throwing away existing const system and starting it
all from scratch with D3. Logical const is harmful
Perhaps the question is too prescriptive. Another way is: Does
D have a big data strategy? But I tried to anchor it to some
currently functioning framework which is why I suggested RDD.
I cannot speak on behalf of the D community. In my opinion I
don't think that it is D that needs a big data
The irony of a thread about "getting [...] out of limbo"
apparently being in limbo is amusing to me.
We've had very few DConf submissions so far, so we're counting on a ton
of them at the last minute.
Please gear up! In terms of participation, this is positively the
largest DConf yet, and we want to make sure the content is up to par!
Andrei
https://www.khronos.org/vulkan/
OS-X Metal is kinda like a C++ derivative => GPU compilation.
With Vulkan/SPIR other languages should be able to come up with
something similar for other platforms.
On Tuesday, 16 February 2016 at 11:20:13 UTC, Johannes Pfau wrote:
Am Tue, 16 Feb 2016 00:28:29 +
schrieb Craig Dillabaugh :
clip
I'd suggest posting this to D.announce, people often don't read
these old threads.
Done! Thanks for the suggestion.
The Google Summer of Code deadline is this Friday.
I would like confirmation from the following individuals if they
can mentor GSOC this summer.
Iain Buclaw
Bruno Medeiros
Martin Nowak (and as backup Admin)
Jacob Ovrum
And as backup mentors
Adam D. Ruppe
Dmitry Olshansky
I know for some
On Tuesday, 16 February 2016 at 13:35:56 UTC, Dicebot wrote:
matter how it is designed. Once you start considering it, you
are better at simply throwing away existing const system and
starting it all from scratch with D3. Logical const is harmful
as it doesn't give and serious guarantees but
On 02/16/2016 02:49 PM, Marc Schütz wrote:
> `@mutable` OTOH would be a useful for both C++, reference counting,
> caching, lazy initialization... But we need to find a way to keep most
> of the existing guarantees, especially concerning shareability.
In my opinion @mutable would be a disaster of
https://issues.dlang.org/show_bug.cgi?id=15661
github-bugzi...@puremagic.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://issues.dlang.org/show_bug.cgi?id=15661
--- Comment #5 from github-bugzi...@puremagic.com ---
Commits pushed to stable at https://github.com/D-Programming-Language/dmd
https://github.com/D-Programming-Language/dmd/commit/5a235b87ddbbdd01e08106ce099f31c72b670043
fix Issue 15661 -
1 - 100 of 160 matches
Mail list logo