On Tuesday, 21 October 2014 at 04:22:37 UTC, thedeemon wrote:
Speaking of this module, since I cannot currently login to
bugtracker, I'd like to note here that there are two major bugs
in one little function: Array.Payload.length setter. One is this
On Sunday, 19 October 2014 at 22:19:05 UTC, Nordlöw wrote:
https://github.com/nordlow/phobos/commit/ce6b9e9ae600b7c28ecddd1e3af7b1516247fb33
now errors as
array.d(927,15): Error: None of the overloads of 'opSlice' are
callable using a const object, candidates are:
array.d(472,25):
On Monday, 20 October 2014 at 10:56:43 UTC, anonymous wrote:
On Sunday, 19 October 2014 at 22:19:05 UTC, Nordlöw wrote:
By the way, since we're in D.learn, I'm assuming you want to do
this yourself. But if you'd like, I could make a pull request
with my suggestions to your branch.
Yes, please!
On Monday, 20 October 2014 at 11:20:30 UTC, Nordlöw wrote:
On Monday, 20 October 2014 at 10:56:43 UTC, anonymous wrote:
On Sunday, 19 October 2014 at 22:19:05 UTC, Nordlöw wrote:
By the way, since we're in D.learn, I'm assuming you want to do
this yourself. But if you'd like, I could make a
On Monday, 20 October 2014 at 18:01:11 UTC, anonymous wrote:
Forgot to mention it here, not sure if you noticed it:
https://github.com/nordlow/phobos/pull/1
Superb.
Speaking of this module, since I cannot currently login to
bugtracker, I'd like to note here that there are two major bugs
in one little function: Array.Payload.length setter. One is this
https://issues.dlang.org/show_bug.cgi?id=13619
and the other is reallocating without notifying GC of the
On Wednesday, 15 October 2014 at 21:15:14 UTC, Nordlöw wrote:
https://github.com/nordlow/phobos/commit/9daf235d7091f76cd941e29e3c167d559bf56a94
but that triggers a new interesting suite of errors
Error: mutable method
std.container.array.Array!int.Array.__fieldPostBlit is not
callable using
On Sunday, 19 October 2014 at 15:21:02 UTC, anonymous wrote:
version(none) _outer = data; /* Error: mutable
method
[...].Array.opAssign is not callable using a
const object */
What do these comments containing Error messages mean? Doesn't
this code compile?
On Sunday, 19 October 2014 at 18:58:50 UTC, Nordlöw wrote:
On Sunday, 19 October 2014 at 15:21:02 UTC, anonymous wrote:
version(none) _outer = data; /* Error: mutable
method
[...].Array.opAssign is not callable using a
const object */
What do these comments
On Sunday, 19 October 2014 at 19:13:33 UTC, anonymous wrote:
Yes, they don't compile. It's three slightly different versions
of initializing _outer.
The first one, `_outer = data;`, is the original one. It's
understandable that it doesn't work anymore with the workaround
in place.
I don't know
On Sunday, 19 October 2014 at 19:30:40 UTC, Nordlöw wrote:
On Sunday, 19 October 2014 at 19:13:33 UTC, anonymous wrote:
Yes, they don't compile. It's three slightly different versions
of initializing _outer.
The first one, `_outer = data;`, is the original one. It's
understandable that it
On Sunday, 19 October 2014 at 20:10:33 UTC, Nordlöw wrote:
Used your ideas here
https://github.com/nordlow/phobos/commit/be6b5f8c4d428a9708a52757a3f31aab6878d379
but unittests now fails as
array.d(234,13): Error: mutable method
std.container.array.Array!int.Array.opAssign is not callable
On Sunday, 19 October 2014 at 20:39:18 UTC, anonymous wrote:
Spell the type out or use `typeof(result)`.
Should be `typeof(return)`.
On Sunday, 19 October 2014 at 15:21:02 UTC, anonymous wrote:
struct RefCounted
{
this(this) /* const doesn't help */ {}
~this() /* const doesn't help */ {}
}
struct Array
{
RefCounted _data;
}
void main() {const Array a; const copy = a;} /* works */
struct RangeM {Array a;}
On Sunday, 19 October 2014 at 20:39:18 UTC, anonymous wrote:
array.d(234,13): Error: mutable method
std.container.array.Array!int.Array.opAssign is not callable
using a const object
You didn't make the change we just discussed.
Change line 234 from `_outer = data;` to `_outer_ = data;`.
You
On Wednesday, 15 October 2014 at 21:15:14 UTC, Nordlöw wrote:
Comint exited abnormally with code 1 at Wed Oct 15 23:14:37
I'm stuck. Need help.
I will give it a try
On Thursday, 16 October 2014 at 13:56:18 UTC, Robert burner
Schadek wrote:
I'm stuck. Need help.
I will give it a try
Thank you.
On Tuesday, 14 October 2014 at 16:08:31 UTC, Robert burner
Schadek wrote:
On Tuesday, 14 October 2014 at 12:51:29 UTC, Nordlöw wrote:
Could you please give me a code example? I'm not skilled
enough in D to follow this description.
struct Range(T) {
Array!S array;
T opIndex(size_t i) {
On Monday, 13 October 2014 at 13:46:56 UTC, Robert burner Schadek
wrote:
other than that I'm not sure how to go about this.
I tried replace inout with a C++-style member duplication at
https://github.com/nordlow/phobos/commit/b2a4ca28bf25bf7c6149566d066cbb54118b36b4
Now it instead errors as
On Monday, 13 October 2014 at 13:46:56 UTC, Robert burner Schadek
wrote:
A blunt force solution would be to create a range as
Range!(ReturnType!Array...)(cast(Array!T)this, low, high);
and then do the correct casts in Range.
The ReturnType would be the ReturnType of opIndex of the Range
type
On Tuesday, 14 October 2014 at 12:51:29 UTC, Nordlöw wrote:
Could you please give me a code example? I'm not skilled enough
in D to follow this description.
struct Range(T) {
Array!S array;
T opIndex(size_t i) {
return cast(T)array[i];
}
}
struct Array(T) {
Range!(const(T))
hm, the problems seams to be that inout Array is not becoming
const Array and friends.
A blunt force solution would be to create a range as
Range!(ReturnType!Array...)(cast(Array!T)this, low, high);
and then do the correct casts in Range.
The ReturnType would be the ReturnType of opIndex of the
On Sunday, 12 October 2014 at 20:17:38 UTC, Nordlöw wrote:
https://github.com/nordlow/phobos/commit/5c57cb18c2b9d340a19d19207deca5af0339cf7e#diff-0
Made some corrections
https://github.com/nordlow/phobos/compare/inout-array-range
but gives a similar error
array.d(223,19): Error: variable
23 matches
Mail list logo
