On Sunday, 13 December 2015 at 22:32:43 UTC, Ilya Yaroshenko
wrote:
Since it's a segfault in the compiler, should I put it on
Bugzilla too?
Yes
1. Please note in Bugzilla report that program code is
incorrect (see example of correct above).
2. More reduced code can be used for report:
void
On Sunday, 13 December 2015 at 15:25:11 UTC, Stefan Frijters
wrote:
On Friday, 11 December 2015 at 22:56:15 UTC, Ilya wrote:
On Friday, 11 December 2015 at 19:31:14 UTC, Stefan Frijters
wrote:
[...]
Slice!(N, T*) arr;
[...]
// compute length
// more flexible
On Friday, 11 December 2015 at 22:56:15 UTC, Ilya wrote:
On Friday, 11 December 2015 at 19:31:14 UTC, Stefan Frijters
wrote:
[...]
Slice!(N, T*) arr;
[...]
// compute length
// more flexible construtors would be added after
// allocatrs support for ndslice
On Sunday, 13 December 2015 at 15:59:19 UTC, Ilya Yaroshenko
wrote:
Could you please post reduced code example that caused dmd to
segfault?
Took dustmite about 6 hours to reduce, and then I went at it
manually for a bit, so this is the smallest I could get it:
import
On Sunday, 13 December 2015 at 21:24:36 UTC, Stefan Frijters
wrote:
On Sunday, 13 December 2015 at 15:59:19 UTC, Ilya Yaroshenko
wrote:
Could you please post reduced code example that caused dmd to
segfault?
Took dustmite about 6 hours to reduce, and then I went at it
manually for a bit, so
On Friday, 11 December 2015 at 19:31:14 UTC, Stefan Frijters
wrote:
Today I've made an abortive attempt at replacing my code's [1]
dependence on unstd.multidimarray [2] with ndslice.
I'm guessing it's just me being stupid, but could anyone supply
with some hints on how to do the conversion with
On Friday, 11 December 2015 at 22:56:15 UTC, Ilya wrote:
On Friday, 11 December 2015 at 19:31:14 UTC, Stefan Frijters
wrote:
Today I've made an abortive attempt at replacing my code's [1]
dependence on unstd.multidimarray [2] with ndslice.
I'm guessing it's just me being stupid, but could
Today I've made an abortive attempt at replacing my code's [1]
dependence on unstd.multidimarray [2] with ndslice.
I'm guessing it's just me being stupid, but could anyone supply
with some hints on how to do the conversion with a minimum of
fuss?
Basically I have an N-dimensional array (N is
On Thursday, 3 December 2015 at 15:07:55 UTC, Andrei Alexandrescu
wrote:
On 12/01/2015 11:03 AM, Jack Stouffer wrote:
On Sunday, 29 November 2015 at 20:53:43 UTC, Jack Stouffer
wrote:
On Monday, 16 November 2015 at 22:45:35 UTC, Jack Stouffer
wrote:
This is the start of the two week formal
On 12/01/2015 11:03 AM, Jack Stouffer wrote:
On Sunday, 29 November 2015 at 20:53:43 UTC, Jack Stouffer wrote:
On Monday, 16 November 2015 at 22:45:35 UTC, Jack Stouffer wrote:
This is the start of the two week formal review
Friendly reminder that the review ends tomorrow.
The two week
On 12/03/2015 10:07 AM, Andrei Alexandrescu wrote:
* The code should use "private" appropriately.
And "package" etc. -- Andrei
On 12/03/2015 11:50 AM, Ilya Yaroshenko wrote:
No functions change data in `ndslice` package.
Then probably "-ed" is appropriate. -- Andrei
On Tuesday, 1 December 2015 at 16:03:51 UTC, Jack Stouffer wrote:
On Sunday, 29 November 2015 at 20:53:43 UTC, Jack Stouffer
wrote:
On Monday, 16 November 2015 at 22:45:35 UTC, Jack Stouffer
wrote:
This is the start of the two week formal review
Friendly reminder that the review ends
On Sunday, 29 November 2015 at 20:53:43 UTC, Jack Stouffer wrote:
On Monday, 16 November 2015 at 22:45:35 UTC, Jack Stouffer
wrote:
This is the start of the two week formal review
Friendly reminder that the review ends tomorrow.
The two week review is over. Thank you to everyone who
On Monday, 16 November 2015 at 22:45:35 UTC, Jack Stouffer wrote:
This is the start of the two week formal review
Friendly reminder that the review ends tomorrow.
On Friday, 20 November 2015 at 21:55:18 UTC, Andrei Alexandrescu
wrote:
On 11/20/15 4:23 PM, Jack Stouffer wrote:
On Friday, 20 November 2015 at 20:33:27 UTC, Ilya wrote:
Great! Added to PR's TODO list :-)
This will be interesting because there is no defined idiomatic
usage of
On Monday, 16 November 2015 at 22:45:35 UTC, Jack Stouffer wrote:
This is the start of the two week formal review for the
proposed std.range.ndslice. This new addition to the standard
library would add the ability to create and manipulate
multi-dimensional random access ranges in a way that
On Wednesday, 18 November 2015 at 10:26:13 UTC, Ilya Yaroshenko
wrote:
On Wednesday, 18 November 2015 at 08:52:11 UTC, Robert burner
Schadek wrote:
I couldn't easily find how to make the module work with
allocators. IMO combining this module with
std.experiemtal.allocator should be possible.
On Friday, 20 November 2015 at 19:21:45 UTC, Jack Stouffer wrote:
On Wednesday, 18 November 2015 at 10:26:13 UTC, Ilya Yaroshenko
wrote:
On Wednesday, 18 November 2015 at 08:52:11 UTC, Robert burner
Schadek wrote:
[...]
I have added makeSlice, however this function can be easily
implemented
On 11/20/15 4:23 PM, Jack Stouffer wrote:
On Friday, 20 November 2015 at 20:33:27 UTC, Ilya wrote:
Great! Added to PR's TODO list :-)
This will be interesting because there is no defined idiomatic usage of
std.allocator. I imagine std.range.ndslice will be the trend-setter for
Phobos in this
On Friday, 20 November 2015 at 20:33:27 UTC, Ilya wrote:
Great! Added to PR's TODO list :-)
This will be interesting because there is no defined idiomatic
usage of std.allocator. I imagine std.range.ndslice will be the
trend-setter for Phobos in this regard.
On Friday, 20 November 2015 at 21:23:40 UTC, Jack Stouffer wrote:
On Friday, 20 November 2015 at 20:33:27 UTC, Ilya wrote:
Great! Added to PR's TODO list :-)
This will be interesting because there is no defined idiomatic
usage of std.allocator. I imagine std.range.ndslice will be the
On Wednesday, 18 November 2015 at 08:52:11 UTC, Robert burner
Schadek wrote:
I couldn't easily find how to make the module work with
allocators. IMO combining this module with
std.experiemtal.allocator should be possible. And if it is
already possible, there should be tests for documentation
On Wednesday, 18 November 2015 at 18:40:40 UTC, Jack Stouffer
wrote:
On Wednesday, 18 November 2015 at 08:52:11 UTC, Robert burner
Schadek wrote:
[...]
I know it's bad practice for regular Phobos code to import from
std.experimental, but what's the protocol for code inside
std.experimental
On Wednesday, 18 November 2015 at 19:25:04 UTC, Ilya wrote:
Possible solutions:
1. Mark `makeSlice` with red "Experimental"
2. Move `makeSlice` to unittest, so user could copy-past it.
Another solution is to leave `makeSlice` in std.experimental when
std.experimental.range.ndslice is moved to
On Monday, 16 November 2015 at 22:45:35 UTC, Jack Stouffer wrote:
This is the start of the two week formal review for the
proposed std.range.ndslice. This new addition to the standard
library would add the ability to create and manipulate
multi-dimensional random access ranges in a way that
On Wednesday, 18 November 2015 at 20:10:00 UTC, Lucien Janvier
wrote:
On Monday, 16 November 2015 at 22:45:35 UTC, Jack Stouffer
wrote:
This is the start of the two week formal review for the
proposed std.range.ndslice. This new addition to the standard
library would add the ability to create
On Tuesday, 17 November 2015 at 18:38:14 UTC, Ilya Yaroshenko
wrote:
Thanks! Implemented:
http://dtest.thecybershadow.net/artifact/website-7a646fdea76569e009844cdee5c93edab10980ca-4f243752aee5ecc098ce1c36eedd86a2/web/phobos-prerelease/std_experimental_range_ndslice.html#byElement
--Ilya
On Wednesday, 18 November 2015 at 08:52:11 UTC, Robert burner
Schadek wrote:
I couldn't easily find how to make the module work with
allocators. IMO combining this module with
std.experiemtal.allocator should be possible. And if it is
already possible, there should be tests for documentation
On Wednesday, 18 November 2015 at 10:18:37 UTC, Nordlöw wrote:
On Tuesday, 17 November 2015 at 18:38:14 UTC, Ilya Yaroshenko
wrote:
AFAIK, if all the slice dimensions are know at compile-time
it should. This is kind of similar to how std.range.chain()
works.
Thanks! Implemented:
I couldn't easily find how to make the module work with
allocators. IMO combining this module with
std.experiemtal.allocator should be possible. And if it is
already possible, there should be tests for documentation and
validation.
On Wednesday, 18 November 2015 at 08:52:11 UTC, Robert burner
Schadek wrote:
I couldn't easily find how to make the module work with
allocators. IMO combining this module with
std.experiemtal.allocator should be possible. And if it is
already possible, there should be tests for documentation
On Tuesday, 17 November 2015 at 18:38:14 UTC, Ilya Yaroshenko
wrote:
AFAIK, if all the slice dimensions are know at compile-time it
should. This is kind of similar to how std.range.chain() works.
Thanks! Implemented:
On Tuesday, 17 November 2015 at 10:16:56 UTC, Nordlöw wrote:
On Tuesday, 17 November 2015 at 10:13:57 UTC, Nordlöw wrote:
Why can't byElement
On Monday, 16 November 2015 at 22:45:35 UTC, Jack Stouffer wrote:
docs:
http://dtest.thecybershadow.net/results/bac6211c1d73b2cf62bc18c9844c8c82c92c21e1/5c6071ca953cf113febd8786b4b68916cbb2cdaf/
I have already posted some things on Github, so If you will
indulge me signing the praises of this
On Tuesday, 17 November 2015 at 00:10:42 UTC, Brian Schott wrote:
On Monday, 16 November 2015 at 22:45:35 UTC, Jack Stouffer
wrote:
This is the start of the two week formal review for the
proposed std.range.ndslice. This new addition to the standard
library would add the ability to create and
On Tuesday, 17 November 2015 at 10:19:26 UTC, Nordlöw wrote:
There seems to be a mis-spelling of experimental as
experemental:
Here:
On Tuesday, 17 November 2015 at 10:13:57 UTC, Nordlöw wrote:
Why can't byElement
http://dtest.thecybershadow.net/artifact/website-7a646fdea76569e009844cdee5c93edab10980ca-2b25fcf8789289fb52e50e2e71914d1a/web/phobos-prerelease/std_experimental_range_ndslice.html#.byElement
provide RandomAccess?
On Monday, 16 November 2015 at 22:45:35 UTC, Jack Stouffer wrote:
docs:
http://dtest.thecybershadow.net/results/bac6211c1d73b2cf62bc18c9844c8c82c92c21e1/5c6071ca953cf113febd8786b4b68916cbb2cdaf/
There seems to be a mis-spelling of experimental as experemental:
Search for:
On Monday, 16 November 2015 at 22:45:35 UTC, Jack Stouffer wrote:
This is the start of the two week formal review for the
proposed std.range.ndslice. This new addition to the standard
Why can't byElement
This is the start of the two week formal review for the proposed
std.range.ndslice. This new addition to the standard library
would add the ability to create and manipulate multi-dimensional
random access ranges in a way that will be very familiar to those
of you who use numpy. This has the
http://forum.dlang.org/post/uesnmkgniumswfclw...@forum.dlang.org
On Monday, 16 November 2015 at 22:45:35 UTC, Jack Stouffer wrote:
This is the start of the two week formal review for the
proposed std.range.ndslice. This new addition to the standard
library would add the ability to create and manipulate
multi-dimensional random access ranges in a way that
43 matches
Mail list logo
