On Tuesday, 13 March 2018 at 12:23:23 UTC, jmh530 wrote:
On Tuesday, 13 March 2018 at 10:35:15 UTC, 9il wrote:
On Tuesday, 13 March 2018 at 04:35:53 UTC, jmh530 wrote:
[snip]
What's TMMat?
TMat is a transposed matrix. Not sure for now if it would be
required.
There are some people who l
On Friday, 12 January 2018 at 22:44:48 UTC, Timon Gehr wrote:
As promised [1], I have started setting up a DIP to improve
tuple ergonomics in D:
https://github.com/tgehr/DIPs/blob/tuple-syntax/DIPs/DIP1xxx-tg.md
[1] https://forum.dlang.org/post/or625h$2hns$1...@digitalmars.com
Awesome!!! Than
On Wednesday, 3 January 2018 at 22:19:41 UTC, jmh530 wrote:
On Wednesday, 3 January 2018 at 19:32:37 UTC, Ilya Yaroshenko
wrote:
Hi, I ported two this functions to mir-algorithm ~master: need
them for work ASAP (License and Copyright are preserved). My
small report:
- Two algorithmic bugs
Hi, I ported two this functions to mir-algorithm ~master: need
them for work ASAP (License and Copyright are preserved). My
small report:
- Two algorithmic bugs in multiwayUnion: it is one line
function, you can easily find them.
- One truly significant algorithmic optimisation bug in
multi
On Monday, 30 October 2017 at 08:34:16 UTC, bauss wrote:
On Monday, 30 October 2017 at 05:48:16 UTC, Ilya Yaroshenko
wrote:
Hi,
I added unittest-release builds into Travis. LDC works well
but DMD fails in few places.
One DMD bug was filled [1]. I will explore others when this is
fixed
Hi,
I added unittest-release builds into Travis. LDC works well but
DMD fails in few places.
One DMD bug was filled [1]. I will explore others when this is
fixed. Please use only LDC for builds with O flag for now.
[1] https://issues.dlang.org/show_bug.cgi?id=17943
Best regards,
Ilya
On Tuesday, 17 October 2017 at 13:36:59 UTC, Kagamin wrote:
Arrays (or in physics-speak, matrices)
multiplied together quite intuitively as:
C = A*B gives an element-by-element multiplication of A and B,
assuming A and B are the same size.
Ehhh?
The same true for ndslice. ndslice returns laz
On Friday, 6 October 2017 at 17:14:51 UTC, Rion wrote:
https://www.quora.com/What-is-your-review-of-D-programming-language
It seems that D still has the GC being mentioned up to today.
Maybe its better to move the standard library slower to a non
gc version in the future...
WIP:
https://git
On Wednesday, 4 October 2017 at 10:03:56 UTC, aberba wrote:
auto {success, message} = callVoldermortFunction();
❤ I want this syntax, plz! This solves the issue how to
return multiple ref values. --Ilya
On Wednesday, 27 September 2017 at 04:59:10 UTC, Manu wrote:
On 26 September 2017 at 21:41, Atila Neves via Digitalmars-d <
digitalmars-d@puremagic.com> wrote:
On Friday, 22 September 2017 at 17:11:56 UTC, Ilya Yaroshenko
wrote:
Should we add `a * b` to ndslice for 1d vectors?
Disc
Should we add `a * b` to ndslice for 1d vectors?
Discussion at https://github.com/libmir/mir-algorithm/issues/91
On Thursday, 7 September 2017 at 20:46:22 UTC, jmh530 wrote:
On Thursday, 7 September 2017 at 12:28:00 UTC, jmh530 wrote:
On Thursday, 7 September 2017 at 12:27:19 UTC, jmh530 wrote:
auto x = data.sliced(2, 3).universal;
Err, (3, 4) not (2, 3)
All kinds of screwed up. This is what I get fo
On Wednesday, 6 September 2017 at 21:44:01 UTC, jmh530 wrote:
On Wednesday, 6 September 2017 at 20:24:05 UTC, Enamex wrote:
Similarly, a[0] has _strides [4, 1] for universal, [4] for
canonical, and [] for contiguous. Mir is written in such a way
that a[0] the same regardless of the SliceKind. F
On Sunday, 3 September 2017 at 12:35:16 UTC, Moritz Maxeiner
wrote:
On Sunday, 3 September 2017 at 09:24:03 UTC, Ilya Yaroshenko
wrote:
On Sunday, 3 September 2017 at 02:43:51 UTC, Moritz Maxeiner
wrote:
On Sunday, 3 September 2017 at 02:08:20 UTC, Ilya Yaroshenko
wrote:
On Tuesday, 29 August
On Sunday, 3 September 2017 at 02:43:51 UTC, Moritz Maxeiner
wrote:
On Sunday, 3 September 2017 at 02:08:20 UTC, Ilya Yaroshenko
wrote:
On Tuesday, 29 August 2017 at 12:50:08 UTC, Robert M. Münch
wrote:
Maybe of interest:
https://www.think-cell.com/en/career/talks/iterators/#1
I haven't
On Tuesday, 29 August 2017 at 12:50:08 UTC, Robert M. Münch wrote:
Maybe of interest:
https://www.think-cell.com/en/career/talks/iterators/#1
I haven't read everything, so not sure if it worth to take a
look.
Iterators has no proper alternative when one need to implement
generic tensor libr
On Thursday, 9 March 2017 at 17:31:53 UTC, Ola Fosheim Grøstad
wrote:
On Saturday, 4 March 2017 at 07:09:17 UTC, Nick Sabalausky
(Abscissa) wrote:
In a similar vein, I have to say I'm thoroughly impressed with
what I've learned of Mir. AIUI, aside from being a fantastic
lib, it looks like a too
On Thursday, 9 March 2017 at 08:59:28 UTC, Ilya Yaroshenko wrote:
Hello
Ndslice got [1] lazy multidimensional concatenation and padding
utilities:
1. stack
2. pad
2. padEdge
3. padSymmetric
4. padWrap
`stack` can be used for ndslices instead of `chain`.
---
import
On Thursday, 9 March 2017 at 08:59:28 UTC, Ilya Yaroshenko wrote:
[1] http://docs.algorithm.dlang.io/latest/mir_ndslice_stack.html
renamed:
http://docs.algorithm.dlang.io/latest/mir_ndslice_concatenation.html
On Thursday, 9 March 2017 at 09:10:47 UTC, Nordlöw wrote:
On Thursday, 9 March 2017 at 08:59:28 UTC, Ilya Yaroshenko
wrote:
Ndslice got [1] lazy multidimensional concatenation and
padding utilities:
Nice. Is this dependent on choosing either RC- or GC-based
allocation?
... continue prev
On Thursday, 9 March 2017 at 09:10:47 UTC, Nordlöw wrote:
On Thursday, 9 March 2017 at 08:59:28 UTC, Ilya Yaroshenko
wrote:
Ndslice got [1] lazy multidimensional concatenation and
padding utilities:
Nice. Is this dependent on choosing either RC- or GC-based
allocation?
No, they are
Hello
Ndslice got [1] lazy multidimensional concatenation and padding
utilities:
1. stack
2. pad
2. padEdge
3. padSymmetric
4. padWrap
`stack` can be used for ndslices instead of `chain`.
---
import mir.ndslice.allocation: slice;
import mir.ndslice.stack: stack;
auto d = stack(a, b, c)
On Sunday, 5 March 2017 at 08:49:33 UTC, Arun Chandrasekaran
wrote:
On Sunday, 5 March 2017 at 05:45:19 UTC, Ilya Yaroshenko wrote:
Why without DRuntime? I had explained this multiple times.
Could this be captured in a wiki or somewhere in a more
positive tone so that new comers are not
On Saturday, 4 March 2017 at 16:43:21 UTC, Moritz Maxeiner wrote:
On Saturday, 4 March 2017 at 15:35:13 UTC, Ilya Yaroshenko
wrote:
[...]
my 1 cent: we should stop trying to convert C++ users.
Please, do no push devs to do not do something. There are two
directions: betterC and DRuntime
On Saturday, 4 March 2017 at 13:24:25 UTC, ketmar wrote:
Nick Sabalausky (Abscissa) wrote:
Just a thought for boosting D's street cred:
Perhaps...take a worthwhile C/C++ project with real potential,
fork it, and port it to D. And make a real commitment to
maintaining it. Obviously a bit of a
2. Canonical:
BLAS-like, raw stride is assumed to be 1
EDIT: row stride
On Wednesday, 8 February 2017 at 15:33:25 UTC, jmh530 wrote:
On Tuesday, 7 February 2017 at 16:18:20 UTC, Ilya Yaroshenko
wrote:
Feedback is welcome!
I don't have time right now to play around with it, but I
looked through the documentation. Here are my comments:
1) I would consider
Hi all,
This is early preview before the announce of Mir Algorithm and
the new ndslice. Ndslice is a dlang package for multidimensional
and numeric worlds.
The new ndslice has three kinds:
1. Universal:
numpy-like, similar to the old ndslice,
2. Canonical:
BLAS-like, raw stride is a
On Wednesday, 4 January 2017 at 21:59:29 UTC, Andrei Alexandrescu
wrote:
On Wednesday, 4 January 2017 at 13:47:53 UTC, Ilya Yaroshenko
wrote:
[...]
We should be able to take care of this with simple
modularization techniques. And there's little worry about
breakage because it&#x
On Wednesday, 4 January 2017 at 10:02:34 UTC, Adam Wilson wrote:
On 1/3/17 11:55 PM, Ilya Yaroshenko wrote:
On Wednesday, 4 January 2017 at 07:32:34 UTC, Adam Wilson
wrote:
Has anything graduated yet?
No
So at what point well we? I mean that is the point after all...
ndslice is
On Wednesday, 4 January 2017 at 07:32:34 UTC, Adam Wilson wrote:
Has anything graduated yet?
No
On Monday, 2 January 2017 at 15:30:34 UTC, Stefan Koch wrote:
On Monday, 2 January 2017 at 15:16:31 UTC, Basile B. wrote:
Write your plan here, and let's take a rendez-vous next year,
to check those plans !!
I plan to improve dmd.
After newCTFE is merged, I will work on the template-subsystem.
On Tuesday, 27 December 2016 at 01:39:18 UTC, Andrei Alexandrescu
wrote:
Walter and I investigated a bit the way C module
initialization/termination works.
https://issues.dlang.org/show_bug.cgi?id=17035 is the result.
This preapproved enhancement would make life easier for folks
who want to w
On Tuesday, 20 December 2016 at 17:28:49 UTC, Stefan Koch wrote:
On Tuesday, 20 December 2016 at 17:15:53 UTC, Ilya Yaroshenko
wrote:
Are they already CTFEable? I have not seen an anounce, sorry
They have been for years now.
Of course only pointers from a CTFE context are valid at ctfe.
The
On Friday, 23 December 2016 at 14:44:41 UTC, rikki cattermole
wrote:
On 24/12/2016 3:14 AM, Russel Winder via Digitalmars-d wrote:
On Wed, 2016-12-21 at 15:49 -0800, Jonathan M Davis via
Digitalmars-d
wrote:
[…]
Anyone who wants to use ldc can use ldc. It doesn't need to
be the
reference
co
On Wednesday, 21 December 2016 at 18:33:52 UTC, Brad Anderson
wrote:
On Wednesday, 21 December 2016 at 16:41:56 UTC, hardreset wrote:
On Wednesday, 21 December 2016 at 16:30:15 UTC, bachmeier
wrote:
On Wednesday, 21 December 2016 at 10:15:26 UTC, hardreset
wrote:
On Tuesday, 20 December 2016 at
On Wednesday, 21 December 2016 at 14:50:31 UTC, thedeemon wrote:
On Wednesday, 21 December 2016 at 11:54:35 UTC, Ilya Yaroshenko
wrote:
On Wednesday, 21 December 2016 at 11:36:14 UTC, thedeemon
wrote:
[...]
If this is true, a blog post about it with more details is
very welcome --Ilya
On Wednesday, 21 December 2016 at 13:18:48 UTC, Andrei
Alexandrescu wrote:
On 12/20/16 6:08 PM, Andrei Alexandrescu wrote:
Hello, a few engineers at Red Hat are taking a look at using
the D
language on the desktop and have reached out to us. They have
created a
list of issues. We are on the top
On Wednesday, 21 December 2016 at 11:54:35 UTC, Ilya Yaroshenko
wrote:
On Wednesday, 21 December 2016 at 11:36:14 UTC, thedeemon wrote:
On Tuesday, 20 December 2016 at 10:18:12 UTC, Kelly Sommers
wrote:
[...]
Bad news: without complete redesign of the language and
turning into one more C
On Wednesday, 21 December 2016 at 11:36:14 UTC, thedeemon wrote:
On Tuesday, 20 December 2016 at 10:18:12 UTC, Kelly Sommers
wrote:
[...]
Bad news: without complete redesign of the language and turning
into one more C++/CLI (where you have different kinds of
pointers in the language for GC a
On Tuesday, 20 December 2016 at 20:51:54 UTC, Andrei Alexandrescu
wrote:
I've asked Joakim about this via email just now, likely other
folks also know the answer:
1. I found these PRs related to local imports:
https://github.com/dlang/phobos/pull/4361
https://github.com/dlang/phobos/pull/4365
On Tuesday, 20 December 2016 at 17:28:49 UTC, Stefan Koch wrote:
On Tuesday, 20 December 2016 at 17:15:53 UTC, Ilya Yaroshenko
wrote:
Are they already CTFEable? I have not seen an anounce, sorry
They have been for years now.
Of course only pointers from a CTFE context are valid at ctfe.
The
On Tuesday, 20 December 2016 at 17:05:03 UTC, Stefan Koch wrote:
On Tuesday, 20 December 2016 at 16:57:34 UTC, Ilya Yaroshenko
wrote:
On Tuesday, 20 December 2016 at 16:34:04 UTC, Walter Bright
wrote:
On 12/20/2016 6:08 AM, Ilya Yaroshenko wrote:
No, tuples stores either value or pointer. If
On Tuesday, 20 December 2016 at 16:34:04 UTC, Walter Bright wrote:
On 12/20/2016 6:08 AM, Ilya Yaroshenko wrote:
No, tuples stores either value or pointer. If it stores
pointer then it is not
safe and it is not CTFE.
You can make it safe by using an array rather than a pointer.
Ranges a
On Tuesday, 20 December 2016 at 16:06:49 UTC, Ilya Yaroshenko
wrote:
On Tuesday, 20 December 2016 at 15:50:03 UTC, Nordlöw wrote:
On Tuesday, 20 December 2016 at 15:42:52 UTC, Ilya Yaroshenko
wrote:
This thread is about mutiple values returned by _reference_.
Tuples can not do it, only
On Tuesday, 20 December 2016 at 15:50:03 UTC, Nordlöw wrote:
On Tuesday, 20 December 2016 at 15:42:52 UTC, Ilya Yaroshenko
wrote:
This thread is about mutiple values returned by _reference_.
Tuples can not do it, only pointers, but they are not ctfeable
and safe
Do pointers worsen
On Tuesday, 20 December 2016 at 15:36:27 UTC, jmh530 wrote:
On Tuesday, 20 December 2016 at 14:56:37 UTC, Ilya Yaroshenko
wrote:
As you can see the output should be 1000, but it is 1.
I was a little confused by what you meant, but the following
main is a little more obvious to me
void
On Tuesday, 20 December 2016 at 14:47:28 UTC, Walter Bright wrote:
On 12/20/2016 5:47 AM, Ilya Yaroshenko wrote:
One good thing for safety and CTFE is allow multiple return
value. In
combination with `auto ref` it is _very_ powerful:
auto ref front()
{
// Returns 2 values, each value
On Tuesday, 20 December 2016 at 14:18:38 UTC, Mike Parker wrote:
On Tuesday, 20 December 2016 at 11:17:19 UTC, Guillaume Piolat
wrote:
Michael Parker is working on that from last I heard.
Yes, he is, though slowly. I can give it more priority after
the New Year.
Thanks for doing this!
On Tuesday, 20 December 2016 at 14:04:26 UTC, Nicholas Wilson
wrote:
On Tuesday, 20 December 2016 at 13:47:50 UTC, Ilya Yaroshenko
wrote:
One good thing for safety and CTFE is allow multiple return
value. In combination with `auto ref` it is _very_ powerful:
auto ref front
One good thing for safety and CTFE is allow multiple return
value. In combination with `auto ref` it is _very_ powerful:
auto ref front()
{
// Returns 2 values, each value is returned by reference if
possible
return (a.front, b.front);
}
Mir libs will use pointers for now. This
On Tuesday, 20 December 2016 at 12:45:13 UTC, Guillaume Piolat
wrote:
On Tuesday, 20 December 2016 at 12:33:27 UTC, John Colvin wrote:
* D used to have 2 standard libraries. That was not a happy
time for the community. People are wary partly because of that.
To bring some cool to the discussio
On Tuesday, 20 December 2016 at 12:49:53 UTC, Walter Bright wrote:
I don't see the need to rewrite cpuid because its sole
dependency on other object files in Druntime is the static
constructor, because the static constructor can be adjusted to
not rely on anything else in Druntime.
If there
On Tuesday, 20 December 2016 at 12:33:27 UTC, John Colvin wrote:
Mir uses deprecated native complex numbers because we can not
spend days explaining why they are better then std.complex (in
short: std.complex breaks compiler optimization logic, function
inlining works, but it breaks optimizati
On Tuesday, 20 December 2016 at 12:00:43 UTC, Walter Bright wrote:
On 12/18/2016 1:02 PM, Ilya Yaroshenko wrote:
I need to understand how it is can be done because I did not
find a valid solution.
mir-cpuid has global symbols, they are accessed using
extern(C) API. If multiple
libraries
On Tuesday, 20 December 2016 at 09:38:58 UTC, rikki cattermole
wrote:
On 20/12/2016 10:32 PM, Ilya Yaroshenko wrote:
On Tuesday, 20 December 2016 at 09:12:55 UTC, Timothee Cour
wrote:
@ilya: regarding -betterC 's stated goal to bypass druntime:
besides static linking (which can be ineffi
On Tuesday, 20 December 2016 at 09:12:55 UTC, Timothee Cour wrote:
@ilya: regarding -betterC 's stated goal to bypass druntime:
besides static linking (which can be inefficient), why not use
runtime
shared libraries to distribute mir (eg GLAS) to C clients ?
IIRC, from a single C++ program, I
On Tuesday, 20 December 2016 at 01:45:27 UTC, Tommi wrote:
Half of the paragraphs contradict the other half. Walter must
headbutt himself in the face reading this.
You may want to try to understand all paragraphs together as a
solid text.
On Monday, 19 December 2016 at 23:03:47 UTC, Mark wrote:
On Monday, 19 December 2016 at 18:38:32 UTC, Ilya Yaroshenko
wrote:
Mir can be translated as "Peace". Cooperation with other
languages through betterC API is more productive than
universality/feature wars :-)
And here I thou
On Monday, 19 December 2016 at 21:00:57 UTC, lurker wrote:
On Monday, 19 December 2016 at 05:59:07 UTC, Ilya Yaroshenko
wrote:
[...]
Thats why I asked for moderation in forums.
+1, and ability to edit own posts.
On Monday, 19 December 2016 at 20:24:21 UTC, Guillaume Piolat
wrote:
On Monday, 19 December 2016 at 20:05:20 UTC, Ilya Yaroshenko
wrote:
[...]
If Mir libs are static libs this can indeed be a problem.
If someone has made another D library like this, it will either
have to be its own dynlib
On Monday, 19 December 2016 at 20:22:29 UTC, Iain Buclaw wrote:
On 19 December 2016 at 20:42, Ilya Yaroshenko via Digitalmars-d
wrote:
On Monday, 19 December 2016 at 19:31:24 UTC, Guillaume Piolat
wrote:
On Sunday, 18 December 2016 at 09:26:09 UTC, Ilya Yaroshenko
wrote:
[...]
If I
On Monday, 19 December 2016 at 19:59:01 UTC, Guillaume Piolat
wrote:
On Monday, 19 December 2016 at 19:54:54 UTC, Ilya Yaroshenko
wrote:
To be more precise: I do not build library exclusively for D.
They should be easily interacted with other languages.
Non sequitur, you can enable the
On Monday, 19 December 2016 at 19:57:45 UTC, Guillaume Piolat
wrote:
On Monday, 19 December 2016 at 19:52:43 UTC, Ilya Yaroshenko
wrote:
How this can work for libraries? Please read this thread.
This is not realistic. This a huge constraint for D libraries
to be modular, replaceable and
On Monday, 19 December 2016 at 19:52:43 UTC, Ilya Yaroshenko
wrote:
On Monday, 19 December 2016 at 19:48:39 UTC, Guillaume Piolat
wrote:
On Monday, 19 December 2016 at 19:42:42 UTC, Ilya Yaroshenko
wrote:
No,
1. DRuntime has not fixed API
Can't you static link with it? If you static
On Monday, 19 December 2016 at 19:48:39 UTC, Guillaume Piolat
wrote:
On Monday, 19 December 2016 at 19:42:42 UTC, Ilya Yaroshenko
wrote:
No,
1. DRuntime has not fixed API
Can't you static link with it? If you static link with it, your
client don't deal with DRuntime.
2.
On Monday, 19 December 2016 at 19:31:24 UTC, Guillaume Piolat
wrote:
On Sunday, 18 December 2016 at 09:26:09 UTC, Ilya Yaroshenko
wrote:
[...]
If I understand correctly, the only reaon not to disable the
runtime instead of going betterC (what I call runtime-free vs
runtime-less) is because
On Monday, 19 December 2016 at 18:38:32 UTC, Ilya Yaroshenko
wrote:
In my Christmas, say for 2050 year...
i wish D to be a default language for multi-language interaction.
https://news.ycombinator.com/item?id=13209861
Mir GLAS [1] raised 11 stars and 138 views during 11 hours
because someone noted it in the discussion.
Interesting note: 4 stars was from Go and Rust developers.
This is small but pleasant proof that D can be a backend language
for high performanc
On Monday, 19 December 2016 at 18:04:14 UTC, safety0ff wrote:
On Sunday, 18 December 2016 at 18:02:58 UTC, Ilya Yaroshenko
wrote:
Thank you for the answer (it is hard to understand me because
English and other reasons),
Ilya
It was difficult to understand your vision until this post, now
On Monday, 19 December 2016 at 01:52:21 UTC, Andrei Alexandrescu
wrote:
On 12/18/16 7:31 PM, Seb wrote:
tl:dr: Phobos is very bloated.
How does the D standard library compare in size with some other
languages (C++, Rust, Go, Java, Python)?
C++ and Rust are the best from this list in terms o
On Monday, 19 December 2016 at 01:33:42 UTC, Mike wrote:
On Sunday, 18 December 2016 at 09:26:09 UTC, Ilya Yaroshenko
wrote:
Who is interested in betterC _modular_* standard library?
What exactly do you mean by "betterC"? As far as I know, the
`-betterC` switch just removes
On Sunday, 18 December 2016 at 20:16:11 UTC, Andrei Alexandrescu
wrote:
On 12/18/2016 03:10 PM, Ilya Yaroshenko wrote:
On Sunday, 18 December 2016 at 19:28:24 UTC, Andrei
Alexandrescu wrote:
On 12/18/2016 01:49 PM, Ilya Yaroshenko wrote:
On Sunday, 18 December 2016 at 17:41:31 UTC, Walter
On Sunday, 18 December 2016 at 19:28:24 UTC, Andrei Alexandrescu
wrote:
On 12/18/2016 01:49 PM, Ilya Yaroshenko wrote:
On Sunday, 18 December 2016 at 17:41:31 UTC, Walter Bright
wrote:
On 12/18/2016 1:26 AM, Ilya Yaroshenko wrote:
We already have better `cpuid` and better `random` packages
On Sunday, 18 December 2016 at 17:41:31 UTC, Walter Bright wrote:
On 12/18/2016 1:26 AM, Ilya Yaroshenko wrote:
We already have better `cpuid` and better `random` packages.
Great! Please PR them for Phobos.
cpuid is used in Mir GLAS and it should be a betterC library.
Without DRuntime
On Sunday, 18 December 2016 at 15:18:37 UTC, Andrei Alexandrescu
wrote:
On 12/18/16 4:26 AM, Ilya Yaroshenko wrote:
Hi,
Who is interested in betterC _modular_* standard library?
I am planing to make libmir org a community for it.
Thought and concerns?
We already have better `cpuid` and better
On Sunday, 18 December 2016 at 15:20:48 UTC, Radu wrote:
2. In the same time many thing is not possible to create with
Phobos/Druntime. The simplest example is numeric libraries. I
can create a multithread GLAS with core.thread, but if I do so
GLAS will never be accepted as default BLAS impleme
On Sunday, 18 December 2016 at 14:37:55 UTC, Radu wrote:
On Sunday, 18 December 2016 at 09:26:09 UTC, Ilya Yaroshenko
wrote:
Hi,
Who is interested in betterC _modular_* standard library?
I am planing to make libmir org a community for it.
Thought and concerns?
We already have better `cpuid
On Sunday, 18 December 2016 at 11:06:58 UTC, Temtaime wrote:
Let's write a D, phobos.
Then we drop all the features and use a BetterC mode.
Then we write all modules against betterC mode.
Sounds like a plan! --Ilya
Hi,
Who is interested in betterC _modular_* standard library?
I am planing to make libmir org a community for it.
Thought and concerns?
We already have better `cpuid` and better `random` packages. The
betterC std.range and std.algorithm analogs would be released
with new ndslice implementation
On Friday, 16 December 2016 at 21:35:23 UTC, John Colvin wrote:
On Friday, 16 December 2016 at 19:14:39 UTC, jmh530 wrote:
On Friday, 16 December 2016 at 17:21:13 UTC, John Colvin wrote:
[...]
It might make sense to provide a sample dub.json file with mir
to make user's lives easier.
That
On Friday, 16 December 2016 at 17:21:13 UTC, John Colvin wrote:
On Friday, 16 December 2016 at 15:09:02 UTC, Ilya Yaroshenko
wrote:
[...]
Do you actually mean extern(C) or extern(D)? You said both at
different points in this thread.
Perhaps this will give you an idea to start from:
name
On Friday, 16 December 2016 at 13:55:55 UTC, Guillaume Piolat
wrote:
Trying to answer with the existing dub.
On Friday, 16 December 2016 at 13:21:53 UTC, Ilya Yaroshenko
wrote:
We need
1. a post fetch (build) options. GLAS should be builded only
in release, and in single file mode. It is a
On Friday, 16 December 2016 at 13:28:49 UTC, rikki cattermole
wrote:
On 17/12/2016 2:21 AM, Ilya Yaroshenko wrote:
Mir GLAS should be builded with special dub flags, in the
future it will
require to be linked with netlib libs.
We need
1. a post fetch (build) options. GLAS should be builded
Mir GLAS should be builded with special dub flags, in the future
it will require to be linked with netlib libs.
We need
1. a post fetch (build) options. GLAS should be builded only in
release, and in single file mode. It is a betterC library with
extern C interface.
2. ability to build C/C++
On Wednesday, 14 December 2016 at 00:18:06 UTC, Joseph Rushton
Wakeling wrote:
Cool. Last question: IIUC you use the private `_z` parameter
as a cache for the most recent `data[index]` value (and AFAICT
that's the only use it has). Is there a good reason for doing
this, rather than just setti
If I remember correctly it is used with Using, so I use the
same type.
Using -> Uint
Sorry, it is phone keyboard
On Tuesday, 13 December 2016 at 18:15:25 UTC, Joseph Rushton
Wakeling wrote:
On Saturday, 26 November 2016 at 20:13:36 UTC, Andrei
Alexandrescu wrote:
Congrats! Also thanks for using the Boost license which would
allow backporting the improvements to Phobos. Who'd be up for
it?
I've finally f
Q4: Current allocator API requires DRuntime to be linked. So,
they are not compatible with BetterC mode. Can this be fixed
before std.experimental.allocator -> std.allocator migration?
--Ilya
On Wednesday, 7 December 2016 at 15:11:36 UTC, jmh530 wrote:
On Wednesday, 7 December 2016 at 11:39:06 UTC, Ilya Yaroshenko
wrote:
Phobos is degrades.
I think I understand what you mean here, but there's definitely
a translation issue.
Yes, my bad. In Russian it has not so big neg
Phobos is degrades. There is a good example:
1. We have BitArray in std.bitmanip:
http://dlang.org/phobos/std_bitmanip.html#.BitArray
2. We are going to add Bitwise, 300+ LOC in std.range
https://github.com/dlang/phobos/pull/4927
The code below represents ndslice implementation.
The benefits
On Wednesday, 30 November 2016 at 20:36:34 UTC, Timon Gehr wrote:
On 30.11.2016 16:22, Ilya Yaroshenko wrote:
Hi,
Mir Random has [1, D] 16 out of 20 [2, C++] random number
distributions.
Remaining 4 are:
1. piecewise_constant_distribution
2. piecewise_linear_distribution
3
Hi,
Mir Random has [1, D] 16 out of 20 [2, C++] random number
distributions.
Remaining 4 are:
1. piecewise_constant_distribution
2. piecewise_linear_distribution
3. binomial_distribution
4. negative_binomial_distribution
[1] http://docs.random.dlang.io/latest/mir_random_variable.html
[2]
ht
On Wednesday, 30 November 2016 at 11:29:25 UTC, Joseph Rushton
Wakeling wrote:
On Tuesday, 29 November 2016 at 08:50:52 UTC, Ilya Yaroshenko
if (isSaturatedRandomEngine!G)
Question on your terminology here: while saturated makes sense,
is it really your intention to restrict things
On Tuesday, 29 November 2016 at 16:54:55 UTC, Nordlöw wrote:
On Saturday, 26 November 2016 at 16:31:40 UTC, Ilya Yaroshenko
wrote:
Bench results:
mir.random 32-bit Mt19937:
6.80851 Gb/s
Does Gb mean Gigabytes or Gigabits?
Gigabits
Hello,
The problem is that a structure for a random algorithm or a
random variable may holds its own precomputed random state, which
is not correct to copy.
From [1] by Joseph Rushton Wakeling:
Essentially the sampling algorithm carries out its own little
internal pseudo-random process which
On Monday, 28 November 2016 at 14:59:28 UTC, Andrei Alexandrescu
wrote:
All language platforms I know of ship with one compiler tied to
one fixed standard library implementation.
We have a small community without commercial support but 3
compilers, large standard library and large ambitions to
On Monday, 28 November 2016 at 14:15:21 UTC, Andrea Fontana wrote:
On Monday, 28 November 2016 at 14:09:10 UTC, Ilya Yaroshenko
wrote:
Instead of "API_LEVEL_DMD_*" this already works:
static if (__VERSION__ >= 2072)
Compiler version should be split from a library versions.
-
On Monday, 28 November 2016 at 14:03:31 UTC, rikki cattermole
wrote:
On 29/11/2016 3:01 AM, Andrea Fontana wrote:
On Monday, 28 November 2016 at 13:51:13 UTC, Andrei
Alexandrescu wrote:
[...]
It's just a simple tag. And I hope that breaking changes are
not that
frequent!
I think that on wor
On Monday, 28 November 2016 at 13:51:13 UTC, Andrei Alexandrescu
wrote:
On 11/28/2016 08:42 AM, Andrea Fontana wrote:
On Monday, 28 November 2016 at 13:34:42 UTC, Andrei
Alexandrescu wrote:
On 11/28/2016 04:13 AM, Andrea Fontana wrote:
Hoping std.v2.stdio works and it's an alias to std.stdio.
1 - 100 of 380 matches
Mail list logo
