What about mutable references to immutable/shared/const classes?
class A {}
immutable(A)[int] aa;
aa[1] = new immutable A;// doesn't compile
Rebindable!(immutable(A))[int]; // looks like ugly shamefull
workaround.
On Wednesday, 13 May 2015 at 15:54:47 UTC, John Colvin wrote:
That's great! I'm looking forward to being able to easily make
direct use of some of the great C++ code out there.
Are there are performance pitfalls to watch out for that are
unique to the way calypso interfaces between D and C++?
Elie,
Congratulations on this very impressive work.
Out of curiosity, how far away do you think it is from being at a
beta stage that one can use to write non-critical work in ?
One open source library that might not be too tough but would
have high value in the financial domain is
On Thursday, 14 May 2015 at 20:23:47 UTC, Laeeth Isharc wrote:
Elie,
Congratulations on this very impressive work.
Out of curiosity, how far away do you think it is from being at
a beta stage that one can use to write non-critical work in ?
Thanks Laeeth,
It's not too far I think. When
An early draft of an expect lib in D.
http://code.dlang.org/packages/dexpect
It includes a sample (and naive) binary implementation that can
read simple expect script files at run time.
I'll be using this in work for automating the testing of a CLI
we're developing that has to run cross
On Wednesday, 13 May 2015 at 15:54:47 UTC, John Colvin wrote:
Are there are performance pitfalls to watch out for that are
unique to the way calypso interfaces between D and C++? E.g.
sneaky copies, implicit callbacks to keep things synced etc.
As I understand, the major remaining issue is
