https://lexi-lambda.github.io/blog/2016/06/12/four-months-with-haskell/#documentation-is-nearly-worthless
- found this on reddit, criticizes haskell docs and praises racket docs:
they are so effective because of how the prose explains what
each function does, when to use it, why you’d use it, an
On Monday, 20 June 2016 at 07:48:49 UTC, Andrea Fontana wrote:
On Saturday, 18 June 2016 at 20:04:50 UTC, Walter Bright wrote:
6. replace std.xml with something we can be proud of that is
second to none in performance (Robert burner Schadek is
mentoring on this https://github.com/lodo1995/expe
On Saturday, 18 June 2016 at 20:04:50 UTC, Walter Bright wrote:
Starting a new thread with this, as requested. There are things
here for all skill levels and time commitments.
3. use -cov to improve code coverage of Phobos unittests
4. make sure every function in Phobos has an example
5. make
On Saturday, 18 June 2016 at 20:04:50 UTC, Walter Bright wrote:
6. replace std.xml with something we can be proud of that is
second to none in performance (Robert burner Schadek is
mentoring on this https://github.com/lodo1995/experimental.xml)
I hope it will support html and xpath too.
Andr
On Sunday, 19 June 2016 at 16:21:36 UTC, Lodovico Giaretta wrote:
Fibers are more of a concurrency than a parallelism tool. Do
you have a link to relevant Chapel description? I am not
familiar with it.
Just found this, although there's probably other material out
there:
http://chapel.cray
On Sunday, 19 June 2016 at 15:40:09 UTC, Dicebot wrote:
On Sunday, 19 June 2016 at 13:32:02 UTC, jmh530 wrote:
On Sunday, 19 June 2016 at 06:19:34 UTC, Dicebot wrote:
Which is inherently suboptimal and is a part of Go marketing
bullshit not worth spending time on. It also requires heavy
runt
On Sunday, 19 June 2016 at 13:32:02 UTC, jmh530 wrote:
On Sunday, 19 June 2016 at 06:19:34 UTC, Dicebot wrote:
Which is inherently suboptimal and is a part of Go marketing
bullshit not worth spending time on. It also requires heavy
runtime modifications (because TLS) unless one wants to
tota
On Sunday, 19 June 2016 at 06:19:34 UTC, Dicebot wrote:
Which is inherently suboptimal and is a part of Go marketing
bullshit not worth spending time on. It also requires heavy
runtime modifications (because TLS) unless one wants to totally
screw plain fibers.
Proper action item instead wou
On Sunday, 19 June 2016 at 09:50:42 UTC, John Colvin wrote:
On Sunday, 19 June 2016 at 01:01:30 UTC, Nicholas Wilson wrote:
On Saturday, 18 June 2016 at 20:04:50 UTC, Walter Bright wrote:
[...]
Now that I'm on my (southern hemisphere) winter break I will
be working on getting LDC to emit PTX
On Sunday, 19 June 2016 at 06:28:45 UTC, deadalnix wrote:
On Sunday, 19 June 2016 at 05:37:01 UTC, Walter Bright wrote:
On 6/18/2016 10:22 PM, Suliman wrote:
8. create a greenthreads module that works like Goroutines
But we already have fibers, I thought that they are same with
Goroutines
On Sunday, 19 June 2016 at 06:37:03 UTC, ZombineDev wrote:
I agree. BTW, what do you think about improving the compiler's
understanding of Fibers (AFAIU they're purely a runtime thing),
so e.g. they're usable at CTFE. See this for more details:
http://lists.llvm.org/pipermail/llvm-dev/2016-Jun
On Sunday, 19 June 2016 at 01:01:30 UTC, Nicholas Wilson wrote:
On Saturday, 18 June 2016 at 20:04:50 UTC, Walter Bright wrote:
9. create a module that enables code to be run on GPUs (John
Colvin is doing work on this, ask him how to help!)
Now that I'm on my (southern hemisphere) winter break
On Sunday, 19 June 2016 at 06:28:45 UTC, deadalnix wrote:
On Sunday, 19 June 2016 at 05:37:01 UTC, Walter Bright wrote:
On 6/18/2016 10:22 PM, Suliman wrote:
8. create a greenthreads module that works like Goroutines
But we already have fibers, I thought that they are same with
Goroutines
On Sunday, 19 June 2016 at 05:37:01 UTC, Walter Bright wrote:
On 6/18/2016 10:22 PM, Suliman wrote:
8. create a greenthreads module that works like Goroutines
But we already have fibers, I thought that they are same with
Goroutines
Fibers are thread local. Goroutines are distributed among
On Sunday, 19 June 2016 at 05:37:01 UTC, Walter Bright wrote:
On 6/18/2016 10:22 PM, Suliman wrote:
8. create a greenthreads module that works like Goroutines
But we already have fibers, I thought that they are same with
Goroutines
Fibers are thread local. Goroutines are distributed among
On 6/18/2016 10:22 PM, Suliman wrote:
8. create a greenthreads module that works like Goroutines
But we already have fibers, I thought that they are same with Goroutines
Fibers are thread local. Goroutines are distributed among fibers and threads,
and can switch from one thread to another.
8. create a greenthreads module that works like Goroutines
But we already have fibers, I thought that they are same with
Goroutines
On 6/18/2016 6:01 PM, Nicholas Wilson wrote:
On Saturday, 18 June 2016 at 20:04:50 UTC, Walter Bright wrote:
9. create a module that enables code to be run on GPUs (John Colvin is doing
work on this, ask him how to help!)
Now that I'm on my (southern hemisphere) winter break I will be working
On Saturday, 18 June 2016 at 20:04:50 UTC, Walter Bright wrote:
9. create a module that enables code to be run on GPUs (John
Colvin is doing work on this, ask him how to help!)
Now that I'm on my (southern hemisphere) winter break I will be
working on getting LDC to emit PTX and SPRIV and if I
On Saturday, 18 June 2016 at 20:04:50 UTC, Walter Bright wrote:
Starting a new thread with this, as requested. There are things
here for all skill levels and time commitments.
There are a good number of things here that are simple to change.
I might make a "How to Start Contributing to D" arti
On 6/18/2016 1:47 PM, Jakob Bornecrantz wrote:
Please don't use the term gorourines when describing a bunch of library
functions. There is more to them then just functions. You will need compiler and
GC support for the special stack that they have.
I know. I just didn't want to write a detailed
On Saturday, 18 June 2016 at 20:04:50 UTC, Walter Bright wrote:
8. create a greenthreads module that works like Goroutines
Please don't use the term gorourines when describing a bunch of
library functions. There is more to them then just functions. You
will need compiler and GC support for th
Starting a new thread with this, as requested. There are things here for all
skill levels and time commitments.
1. eliminate all gratuitous use of gc
2. review all Phobos modules for compatibility with ranges - std.zip, for
example, was done before ranges and does not work with them
3. use -
23 matches
Mail list logo
