On 4/13/2015 7:48 PM, weaselcat wrote:
On Tuesday, 14 April 2015 at 02:45:37 UTC, weaselcat wrote:
On Tuesday, 14 April 2015 at 02:39:40 UTC, Walter Bright wrote:
On 4/13/2015 7:23 PM, weaselcat wrote:
this is essentially fusion/deforestation, correct?
??
weaselcat:
It's reddit, that's not really surprising.
Do you know a place better than Reddit for general programming
discussions?
The lambda the ultimate blog is not generic.
Bye,
bearophile
On 4/14/2015 12:24 AM, bearophile wrote:
Walter Bright:
Algorithms don't actually do deforestation or fusion. The magic happens in how
the algorithm is implemented, i.e. the elements are created lazily (on demand)
rather than eagerly.
Stream fusion is often about laziness. There is a ton of
Walter Bright:
Algorithms don't actually do deforestation or fusion. The magic
happens in how the algorithm is implemented, i.e. the elements
are created lazily (on demand) rather than eagerly.
Stream fusion is often about laziness. There is a ton of
literature about this topic.
Bye,
https://www.reddit.com/r/programming/comments/32f4as/why_most_high_level_languages_are_slow/
Good article, discussion is a bit lame.
On Monday, 13 April 2015 at 23:28:46 UTC, Walter Bright wrote:
Good article, discussion is a bit lame.
It's reddit, that's not really surprising.
On Mon, Apr 13, 2015 at 04:28:45PM -0700, Walter Bright via Digitalmars-d wrote:
https://www.reddit.com/r/programming/comments/32f4as/why_most_high_level_languages_are_slow/
Good article, discussion is a bit lame.
While Phobos is making good progress at being allocation-free, it still
has a
On Tuesday, 14 April 2015 at 02:12:18 UTC, Walter Bright wrote:
On 4/13/2015 4:28 PM, Walter Bright wrote:
https://www.reddit.com/r/programming/comments/32f4as/why_most_high_level_languages_are_slow/
Good article, discussion is a bit lame.
One of the reasons I've been range-ifying Phobos is
thanks for the links and colour, Walter and HST
But at the end of the day, the programmer has to know how to
write
cache-efficient code. No matter how the language/compiler tries
to be
smart and do the Right Thing(tm), poorly-laid out data is
poorly-laid
out data, and you're gonna incur cache
On 4/13/2015 4:28 PM, Walter Bright wrote:
https://www.reddit.com/r/programming/comments/32f4as/why_most_high_level_languages_are_slow/
Good article, discussion is a bit lame.
One of the reasons I've been range-ifying Phobos is not only to remove
dependence on the GC, but often to eliminate
On Tuesday, 14 April 2015 at 02:44:15 UTC, Laeeth Isharc wrote:
thanks for the links and colour, Walter and HST
But at the end of the day, the programmer has to know how to
write
cache-efficient code. No matter how the language/compiler
tries to be
smart and do the Right Thing(tm),
On Tuesday, 14 April 2015 at 02:39:40 UTC, Walter Bright wrote:
On 4/13/2015 7:23 PM, weaselcat wrote:
this is essentially fusion/deforestation, correct?
??
http://en.wikipedia.org/wiki/Deforestation_(computer_science)
On Tuesday, 14 April 2015 at 02:45:37 UTC, weaselcat wrote:
On Tuesday, 14 April 2015 at 02:39:40 UTC, Walter Bright wrote:
On 4/13/2015 7:23 PM, weaselcat wrote:
this is essentially fusion/deforestation, correct?
??
http://en.wikipedia.org/wiki/Deforestation_(computer_science)
my bad,
On 4/13/2015 7:23 PM, weaselcat wrote:
this is essentially fusion/deforestation, correct?
??
On Tuesday, 14 April 2015 at 02:23:08 UTC, weaselcat wrote:
On Tuesday, 14 April 2015 at 02:12:18 UTC, Walter Bright wrote:
On 4/13/2015 4:28 PM, Walter Bright wrote:
https://www.reddit.com/r/programming/comments/32f4as/why_most_high_level_languages_are_slow/
Good article, discussion is a bit
15 matches
Mail list logo
